Open Stack

> On Jan 25, 2018, at 21:23, Logan V. <logan at protiumit.com> wrote:
> 
> There is a small patch in the bug which resolves the config drive
> ordering. Without that patch I don't know of any workaround. The
> config drive will always end up first in the boot order and the
> instance will always fail to boot in that situation.
> 
> For the multi-volume instances where the boot volume is out of order,
> I don't know of any patch for that. One workaround is to detach any
> secondary data volumes from the instance, and then reattach them after
> booting from the one and only attached boot volume.

I’ve posted an addition to the small patch in the launchpad bug intended to handle the multi-volume problem.

If there’s any way you could try that out and let us know if it fixes things for your case, it would help us out a lot.

-melanie