Volume status ERRORs in c-api after successful tempest run

[David Kranz]

2013-11-26 02:07:24.191 25993 ERROR cinder.volume.api [req-2ba1e9a2-1560-4678-9df7-8bcf527c8a05 63290b1383dd4d05a8ddce92b0164523 42f4a98cd9aa4b8aa2dc90761db9aa11] Volume status must be available to reserve
2013-11-26 02:07:24.468 25993 ERROR cinder.api.openstack.wsgi [req-45a146f8-38b0-46f6-afdc-77cabedbb152 63290b1383dd4d05a8ddce92b0164523 42f4a98cd9aa4b8aa2dc90761db9aa11] Exception handling resource: int() argument must be a string or a number, not 'NoneType'
 2013-11-26 02:08:28.268 25993 ERROR cinder.volume.api [req-dc6a565b-689b-4403-85a8-46cde6a995f7 c7fdc2f644364883a2471f53f62e22b7 198ad1ed7354470a995b7bb822a7e7cc] Volume status must be available to reserve

These happen quite frequently.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/58855

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/58855
Committed: http://github.com/openstack/cinder/commit/e6a1ba529172b14eed6f611a1d6a09e673176dfd
Submitter: Jenkins
Branch: master

commit e6a1ba529172b14eed6f611a1d6a09e673176dfd
Author: john-griffith <email address hidden>
Date: Wed Nov 27 14:02:48 2013 -0700

    Handle NotFound exception in snapshots API code

    Passing tests in the gate leave unhandled trace/error messages
    for a VolumeNotFound issue.

    These are caused by the test_volumes_snapshots_negative test
    which requests a non-existent volume and the tests pass however
    the log files are a bit messed up due to the unhandled exception.

    This change just adds a try/catch block around the volume get calls
    in the snapshot modules and raises HTTPNotFound as appropriate.

    Change-Id: I2096f2da7c68ef7924fc8e69b2d5c2afea578512
    Closes-Bug: #1255214