[Openstack-security] [Bug 1369627] Change abandoned on nova (master)
OpenStack Infra
1369627 at bugs.launchpad.net
Wed May 13 17:20:53 UTC 2015
Change abandoned by Joe Gordon (joe.gordon0 at gmail.com) on branch: master
Review: https://review.openstack.org/123073
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.
--
You received this bug notification because you are a member of OpenStack
Security, which is subscribed to OpenStack.
https://bugs.launchpad.net/bugs/1369627
Title:
libvirt disk.config will have issues when booting two with different
config drive values
Status in OpenStack Compute (Nova):
Fix Released
Status in OpenStack Security Advisories:
Won't Fix
Bug description:
Currently, in the image creating code for Juno we have
if configdrive.required_by(instance):
LOG.info(_LI('Using config drive'), instance=instance)
image_type = self._get_configdrive_image_type()
backend = image('disk.config', image_type)
backend.cache(fetch_func=self._create_configdrive,
filename='disk.config' + suffix,
instance=instance,
admin_pass=admin_pass,
files=files,
network_info=network_info)
The important thing to notice here is that we have
"filename='disk.confg' + suffix". This means that the filename for
the config drive in the cache directory will be simply 'disk.config'
followed by any potential suffix (e.g. '.rescue'). This name is not
unique to the instance whose config drive we are creating. Therefore,
when we go to boot another instance with a different config drive, the
cache function will detect the old config drive, and decide it doesn't
need to create the new config drive with the appropriate config for
the new instance.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1369627/+subscriptions
More information about the Openstack-security
mailing list