yahoo-eng-team team mailing list archive

[OpenStack Infra <1733736@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/522112
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ca6daf148debb9c9646fcf6db9660c830da5a594
Submitter: Zuul
Branch:    master

commit ca6daf148debb9c9646fcf6db9660c830da5a594
Author: lixipeng <lixipeng@xxxxxxxxxxxxx>
Date:   Wed Nov 22 12:03:58 2017 +0800

    Fix bug case by none token context
    
    When set reclaim_instance_interval > 0, and then delete an
    instance which booted from volume with `delete_on_termination`
    set as true. After reclaim_instance_interval time pass,
    all volumes boot instance will with state: attached and in-use,
    but attached instances was deleted.
    
    This bug case as admin context from
    `nova.compute.manager._reclaim_queued_deletes` did not have
    any token info, then call cinder api would be failed.
    
    So add user/project CONF with admin role at cinder group,
    and when determine context is_admin and without token, do
    authenticaion with user/project info to call cinder api.
    
    Change-Id: I3c35bba43fee81baebe8261f546c1424ce3a3383
    Closes-Bug: #1733736
    Closes-Bug: #1734025
    Partial-Bug: #1736773


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  reclaim_instance_interval causes dirty attached volume

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  Description

  When set reclaim_instance_interval > 0, and we delete an instance which boot from volume with delete_on_termination set as true.
  After reclaim_instance_interval time pass, all volumes boot instance will with state: attached and in-use, but attached instances was deleted.

  Steps to reproduce

  1. set reclaim_instance_interval = 60
  2. create a bootable volume
  3. boot instance with created bootable volume
  4. delete instance, and wait 60 seconds

  Expected result

  Previous test bootable volume was deleted after
  reclaim_instance_interval seconds.

  Actual result

  Previous test bootable volume was in state attached and in-use,
  attached with deleted instance.

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