Description of problem: config_drive_cdrom = false should ensure the config drive will be HDD, not a CD ROM, but it is ineffective. Nova creates VM with <disk type="file" device="cdrom"> <driver name="qemu" type="raw" cache="none"/> <source file="/var/lib/nova/instances/3eeb598a-6871-49bf-8016-fb519531e296/disk.config"/> <target bus="ide" dev="hdd"/> </disk> cloud-init doesn't detecting this disk, fallbacks to network metadata discovery and because of bug BZ#984311, it keeps outputting 2013-08-15 17:22:37,764 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [85/120s]: url error [[Errno 113] No route to host] for several minutes upon boot. Version-Release number of selected component (if applicable): openstack-nova-common-2013.1.3-1.el6ost.noarch openstack-nova-compute-2013.1.3-1.el6ost.noarch How reproducible: 1/1 Steps to Reproduce: 1. openstack-config --set /etc/nova/nova.conf HYPERV config_drive_cdrom false 2. openstack-config --set /etc/nova/nova.conf DEFAULT config_drive_cdrom false 3. for svc in /etc/init.d/openstack-*; do $svc condrestart; done 4. boot an instance 5. observe the log, or check whether the config disk is an sr0 /dev/disk/by-label/config-2 ../../sr0 Actual results: disk is CDROM Expected results: disk is HDD (/dev/vdb) Additional info: Setting urgen because it is kinda regression and it causes workaround of other bug ineffective.
ndipanov adivced to set openstack-config --set /etc/nova/nova.conf DEFAULT config_drive_format vfat this did the trick. Config drive is now back a HDD.
So we need a relnote?
Nikola will change default in nova-dist.conf so we don't need RHOS relnote. For upstream I've added a relnote in https://wiki.openstack.org/wiki/ReleaseNotes/2013.1.3#Known_Issues_and_Limitations
Verified openstack-nova-2013.1.3-2 (puddle 2013-08-20.1): Followed the bug steps - after I set debug=True in nova.conf -> it allowed to observe the Instance creation XML in compute.log, that include: disk type="file" device="disk"
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-1199.html