Description of problem: Do we support rescuing a volume backed instance in OSP9? I found a similar upstream bug for Icehouse version and seems that it was not supported at that time: https://bugs.launchpad.net/nova/+bug/1453779 Is it possible to include this feature in future OSP releases? Version-Release number of selected component (if applicable): OSP9 How reproducible: Always Steps to Reproduce: 1. Boot an instance from a volume. 2. Try to rescue it using 'nova rescue <id>' Actual results: Cannot rescue a volume backed instance Expected results: Should be able to rescue volume backed instance
No, this isn't supported. There is work upstream to make fundamental changes to the way rescue works in the libvirt driver, but it is not currently on the upstream priority list. I'm going to mark this as an RFE.
Lee's original patch series: https://review.openstack.org/#/q/project:openstack/nova+branch:master+topic:bp/virt-rescue-stable-disk-devices
*** Bug 1492226 has been marked as a duplicate of this bug. ***
Is it possible to triage this RFE? BR, Alex.
There is an upstream BP: https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rescue
Hi Team, Are there plans to backport this to OSP16? Thank you.
(In reply to ldenny from comment #10) > Hi Team, > > Are there plans to backport this to OSP16? > > Thank you. No, we unfortunately can't backport this to OSP16 given the required API changes.
TRAC team have stated there will be no RFEs in zstreams for OSP 17.0 so moving this to 17.1. Any questions please contact rhos-trac.
This will need an enhancement doctext once this graduates out of tech preview (https://bugzilla.redhat.com/show_bug.cgi?id=2120743)
Closing as CURRENTRELEASE. The code is present in 17.0 and 17.1, but no further QE work will be performed due to lack of capacity. This puts this RFE into the "implicitly supported" category like most Nova features that originate in the community and that appear in our OSP code without much involvement from Red Hat engineers. If a significant enough bug ends up being reported for this feature, we will re-evaluate the QE situation. There will, however, be documentation written for this feature: https://issues.redhat.com/browse/RHOSPDOC-1275.