yahoo-eng-team team mailing list archive

[Hironori Shiina <shiina.hironori@xxxxxxxxxxxxxx>]

Public bug reported:

For creating instance with booting from a volume, the volume is reserved
before scheduling[1]. When the scheduling is failed due to lack of valid
hosts, the instance gets in ERROR state and the volume is kept in
'attaching' state. The volume reservation is not removed even if the
instance is deleted.

[1]
https://github.com/openstack/nova/blob/5d3a11b9c9a6a5aecd46ad7ecc635215184d930e/nova/compute/api.py#L3577

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Volume is not unreserved after schduling is failed

Status in OpenStack Compute (nova):
  New

Bug description:
  For creating instance with booting from a volume, the volume is
  reserved before scheduling[1]. When the scheduling is failed due to
  lack of valid hosts, the instance gets in ERROR state and the volume
  is kept in 'attaching' state. The volume reservation is not removed
  even if the instance is deleted.

  [1]
  https://github.com/openstack/nova/blob/5d3a11b9c9a6a5aecd46ad7ecc635215184d930e/nova/compute/api.py#L3577

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