yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #00595
[Bug 1101048] Re: Baremetal pxe driver doesn't delete /tftpboot/{uuid}/*
** Changed in: nova
Status: Fix Committed => Fix Released
** Changed in: nova
Milestone: None => grizzly-3
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1101048
Title:
Baremetal pxe driver doesn't delete /tftpboot/{uuid}/*
Status in OpenStack Compute (Nova):
Fix Released
Bug description:
Baremetal PXE driver deactivate_bootloader() is failing to delete tftp
images when driver.destroy() is called. This results in a non-empty
/tftpboot/{instance-uuid}/ directory being left behind on the compute
node after an instance is deleted.
I believe this happens because the instance parameter passed to
driver.destroy() does not contain ['extra_specs']['deploy_kernel_id']
or ['extra_specs']['deploy_ramdisk_id']. These these were passed to
driver.spawn(), so I had assumed they were passed to driver.destroy()
as well. This can be confirmed by logging the exception within the
first try: block of deactivate_bootloader().
One solution is to pass extra_specs to driver.destroy().
Another solution is for deactivate_bootloader() to blindly delete all files under the /tftpboot/{instance-uuid}/ directory.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1101048/+subscriptions