The DocImpact was resolved with an update of the support matrix within
the same patch [1]. No further docs need an update.

References:
[1] 
https://github.com/openstack/nova/commit/3f96f3039a17e2cad15c05c#diff-9285e4a9e182215df250d22736c79824R360

** Changed in: nova
       Status: New => Invalid

-- 
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/1584554

Title:
      Hyper-V: Implement nova rescue

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  https://review.openstack.org/127159
  Dear bug triager. This bug was created since a commit was marked with 
DOCIMPACT.
  Your project "openstack/nova" is set up so that we directly report the 
documentation bugs against it. If this needs changing, the docimpact-group 
option needs to be added for the project. You can ask the OpenStack infra team 
(#openstack-infra on freenode) for help if you need to.

  commit 3f96f3039a17e2cad15c05c4fe2d61ee16a14a80
  Author: Lucian Petrut <lpet...@cloudbasesolutions.com>
  Date:   Fri Feb 6 19:02:23 2015 +0200

      Hyper-V: Implement nova rescue
      
      The root disk image is moved to a separate disk slot while the
      rescue image will take it's place. If the instance requires it,
      a temporary config drive is created as well.
      
      Unrescuing the instance will move the root disk image back in
      place, removing temporary images.
      
      DocImpact
      
      Implements: blueprint hyper-v-rescue
      
      Change-Id: I6059ae35a77d675f54b98b2b43b5762e1d24365b

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1584554/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to