Ironic in MOS supports only Ubuntu 14 images to boot

[Kyrylo Romanenko]

On current MOS release, Ironic supports booting of real baremetal and virtual instances without additional preparations only for Ubuntu 14.04 Trusty Tahr cloud image.

Link to image:
https://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64.tar.gz

Other images like older Ubuntu 12, actual Fedora Server 23 and Debian 8.2.0 are not suitable in out-of-the-box state.

To deploy other operating systems via Ironic in MOS customer will be required to enable specific driver, get bootstrap images.

We need to add this to Release Notes.

[Roman Podoliaka (rpodolyaka)]

Isn't up to operators to create correct images?

[Kyrylo Romanenko (kromanenko)]

Roman, yes, images can be prepared by operators. But without additional preparations out-of-the-box we can run only Ubuntu Trusty image.

[Roman Podoliaka (rpodolyaka)]

Well, my point is, that's not a bug: we provide ubuntu trusty images as default ones to be used, if operators want to add other images - they are more than welcome to do that. It's up to them, though, to make sure they include all required drivers for the hardware used.

[Roman Podoliaka (rpodolyaka)]

Ok, let's make sure we document this and re-evaluate again for 9.0

[Roman Podoliaka (rpodolyaka)]

Per discussion with the Ironic team, this is not a known issue, but rather an idea, how to imporve our docs.

[Dina Belova (dbelova)]

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

[Kyrylo Romanenko (kromanenko)]

I took to recheck this issue with MOS 10.

[Kyrylo Romanenko (kromanenko)]

Passed both ironic_deploy_swift and ironic_deploy_ceph tests on custom CI with MOS 10.
ironic_deploy_ceph:
https://custom-ci.infra.mirantis.net/job/10.0.custom.system_test/1684/console
ironic_deploy_swift:
https://custom-ci.infra.mirantis.net/job/10.0.custom.system_test/1687/console
Test patch: https://review.openstack.org/#/c/454188/

Used iso: fuel-10.0-1570-2017-04-05%5F17-00-00.iso

[Kyrylo Romanenko (kromanenko)]

I set this bug to Invalid for 10.0 because tests with Ubuntu Xenial (16) passed successfully.