Hide Forgot
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue. Description: Current workflow: When a rescue is done on an instance, the image_base_ref in the instance_meta_data is used. In the case where this attribute is not populated, the custom image_ref is used instead. This poses a problem where the custom image used might be corrupt leading to errors, or too large leading to timeouts. Also, if the base image is deleted, the image ref on the instance_system_metadata will be invalid, leading to the rescue operation failing. The user should be allowed to specify which image is to be used for rescue. (could be a default base image or a custom image). Specification URL (additional information): None
This bug has been closed as a part of the RHEL-OSP 6 general availability release. For details, see https://rhn.redhat.com/errata/rhel7-rhos-6-errata.html
Hi, Sorry for re-opening this bug. In a fresh packstack OSP6 all in one environment, I don't see the option --image when rescuing an instance. # nova help rescue usage: nova rescue <server> Reboots a server into rescue mode, which starts the machine from the initial image, attaching the current boot disk as secondary. Positional arguments: <server> Name or ID of server. # rpm -qf $(which nova) python-novaclient-2.20.0-1.el7ost.noarch If I misunderstand anything please kindly let me know. Best Regard, Chen
You need a newer novaclient. This feature was first introduced in 2.21.0.
Hi Russell, Thank you for your reply. The newest novaclient version in OSP 6.0 is 2.20.0-1 now. So how could this feature be imported in OSP 6.0 GA version ? Best Regards, Chen
The latest version of python-novaclient in RHOS6 is older (as of 2016-06-08.2) . So the bug cannot be verified at the moment until newer client is packaged. [root@serverA ~(keystone_admin)]# yum list installed |grep python-novaclient python-novaclient.noarch 1:2.20.0-1.el7ost @rhelosp-6.0-puddle