yahoo-eng-team team mailing list archive

[OpenStack Infra <1750666@xxxxxxxxxxxxxxxxxx>]

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

commit 3120627d9802ceda46c2db387fec8fbc80700338
Author: Mohammed Naser <mnaser@xxxxxxxxxxxx>
Date:   Tue Feb 20 16:47:06 2018 -0500

    Add functional test for deleting BFV server with old attach flow
    
    When creating a new instance and deleting it before it gets scheduled
    with the old attachment flow (reserve_volume), the block device mappings
    are not persisted to database which means that the clean up fails
    because it tries to lookup attachment_id which cannot be lazy loaded.
    
    This patch adds a (failing) functional test to check for this issue
    which will be addressed in a follow-up patch.
    
    Related-Bug: #1750666
    Change-Id: I294c54e5a22dd6e5b226a4b00e7cd116813f0704


** 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/1750666

Title:
  Deleting an instance before scheduling with BFV fails to detach volume

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  If you try to boot and instance and delete it early before scheduling,
  the '_delete_while_booting' codepath hits
  `_attempt_delete_of_buildrequest` which tries to remove the block
  device mappings.

  However, if the cloud contains compute nodes before Pike, no block
  device mappings will be present in the database (because they are only
  saved if using the new attachment flow), which means the attachment
  IDs are empty and the volume delete fails:

  2018-02-20 16:02:25,063 WARNING [nova.compute.api] Ignoring volume
  cleanup failure due to Object action obj_load_attr failed because:
  attribute attachment_id not lazy-loadable

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