autopilot newton with horizon, can't launch instances with default settings

[David Britton]

dpb │ Error: Failed to perform requested operation on instance "test-dpb", the instance has an error status: Please try again later [Error: Build of instance 34dbc854-64ae-425c-a4e6-6522032893f0 aborted: Block Device Mapping is Invalid.

Needs investigation.

Workaround: uncheck 'create new volume' when launching the instance.

[Alberto Donato (ack)]

It seems defaults changed in Horizon, it doesn't seem something we can do on the Landscape side.

FWIW the volume should be eventually created, but it takes longer than the retries Nova does to check if the volume is ready. So it eventually gives up and the image build fails.

[Chad Smith (chad.smith)]

Just reproduced on the lp:landscape cloud deployment

Error: Failed to perform requested operation on instance "test", the instance has an error status: Please try again later [Error: Build of instance 6fd6e315-99fb-43fd-af7e-821135b222ca aborted: Block Device Mapping is Invalid.].

[Chad Smith (chad.smith)]

Will close when we update release notes documentation.

[Andreas Hasenack (ahasenack)]

landscape server status is "wontfix" actually, since we didn't change anything and don't plan to.

[Frode Nordahl (fnordahl)]

The root cause of this issue is in Horizon itself see bug 1560965

[Frode Nordahl (fnordahl)]

Looking a bit further into this the horizon bug mentioned in #5 comes into play in some circumstances when using iSCSI as block storage back-end.

There is however a separate and different issue leading to similar results present on Autopilot deployed clouds using Ceph as block storage back-end.

I will follow-up with more details about this in a separate bug report.

[James Page (james-page)]

Bug is in OpenStack (bug 1560965); marking charm task as invalid.