Bug 1041119

Summary:	[RFE][nova]: Allow user to specify image to use during rescue
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	openstack-nova	Assignee:	Russell Bryant <rbryant>
Status:	CLOSED WONTFIX	QA Contact:	Prasanth Anbalagan <panbalag>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	cchen, eglynn, markmc, panbalag, sgordon, srevivo, stoner, trichard
Target Milestone:	ga	Keywords:	FutureFeature, Reopened, Triaged, ZStream
Target Release:	6.0 (Juno)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/allow-image-to-be-specified-during-rescue
Whiteboard:	upstream_milestone_juno-2 upstream_status_implemented upstream_definition_approved
Fixed In Version:	openstack-nova-2014.2.1-11.el7ost	Doc Type:	Enhancement
Doc Text:	Previously, when a rescue was done on an instance, the image_base_ref in the instance_meta_data was used. If this attribute was not populated, the custom image_ref was used instead. This posed a problem where the custom image used might be corrupt, leading to errors; or too large, leading to timeouts. Also, if the base image was deleted, the image ref on the instance_system_metadata would be invalid, leading to the rescue operation failing. With this release, the user can now specify which image is to be used for rescue (this could be a default base image, or a custom image).	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-06-17 19:32:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 13:41:59 UTC

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

Comment 6 Scott Lewis 2015-02-09 20:04:54 UTC

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

Comment 7 Chen 2016-02-17 10:04:25 UTC

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

Comment 8 Russell Bryant 2016-02-17 14:45:51 UTC

You need a newer novaclient.  This feature was first introduced in 2.21.0.

Comment 9 Chen 2016-02-18 01:37:36 UTC

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

Comment 11 Prasanth Anbalagan 2016-06-15 20:39:55 UTC

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