← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1713735] Re: Nova assisted volume snapshots fails to find BDM in multi-cell

 

Reviewed:  https://review.openstack.org/498845
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=074614f07751f3a10e630fc7344a0794516bb32b
Submitter: Jenkins
Branch:    master

commit 074614f07751f3a10e630fc7344a0794516bb32b
Author: Lucian Petrut <lpetrut@xxxxxxxxxxxxxxxxxxxxxx>
Date:   Tue Aug 29 17:30:18 2017 +0300

    Fix nova assisted volume snapshots
    
    When performing nova assisted volume snapshots, the nova api does
    not receive an instance id, so there is not the usual instance
    lookup from the cell which automatically targets the context for the
    cell that the instance was pulled from, which is also where we'd get
    the BDM.
    
    Since we do not know which cell to target when fetching the BDM, we
    have to iterate through *all* of them.
    
    Closes-Bug: #1713735
    
    Change-Id: Id2e3d3f177739a31d63790e4a1ae6ac41f438ddd


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

Title:
  Nova assisted volume snapshots fails to find BDM in multi-cell

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  When using separate databases for each Nova cell, nova assisted volume snapshots always fail with the following error:
  BadRequest: No volume Block Device Mapping with id a10bd120-9b88-4710-bf6e-f1d34de87da2. (HTTP 400)

  The reason is that the according API call does not include an instance
  id, which is fetched from the BDM. At the same time, the BDM cannot
  properly be retrieved since Nova doesn't know which cell to use,
  looking for the BDM in the wrong DB.

  Cinder trace: http://paste.openstack.org/raw/619767/

  Among others, Cinder NFS backends are affected by this, as per the following Cinder NFS CI logs:
  http://logs.openstack.org/21/498321/5/check/gate-tempest-dsvm-full-devstack-plugin-nfs-nv/b8bca96/logs/screen-c-vol.txt.gz?level=ERROR

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


References