Comment 12 for bug 1371677

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to nova (master)

Reviewed: https://review.openstack.org/122873
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a570111d953f7b2a5bd2b4f47dda353f2aba78c
Submitter: Jenkins
Branch: master

commit 9a570111d953f7b2a5bd2b4f47dda353f2aba78c
Author: Matt Riedemann <email address hidden>
Date: Fri Sep 19 12:49:31 2014 -0700

    Handle volume bdm not found in lvm.get_volume_size

    We're stack tracing in successful gate runs because of a race when
    deleting an instance and when the update_available_resource periodic
    task is running.

    When we hit the race, the volume that's backing the instance is deleted
    and the periodic task (virt driver) is trying to get the current
    information about the volume, which no longer exists and we fail and
    short-circuit the update_available_resource task.

    This change adds a decorator which checks if a ProcessExecutionError is
    due to the device no longer existing and if so, raises
    VolumeBDMPathNotFound, and applies that decorator to the get_volume_size
    method.

    Related-Bug: #1371677

    Change-Id: Ic452df82c61087efda8d742e030076421c0c813b