Public bug reported: Ever since https://review.openstack.org/#/c/374373/ and https://review.openstack.org/#/c/399735/ merged today I've seen at least two changes in the gate get bumped out due to the swap volume test failing in the cells v1 job, seen here:
http://logs.openstack.org/06/425806/8/check/gate-tempest-dsvm-cells- ubuntu-xenial/ab0bba2/console.html#_2017-01-31_01_48_47_209159 2017-01-31 01:48:47.209256 | Captured traceback: 2017-01-31 01:48:47.209267 | ~~~~~~~~~~~~~~~~~~~ 2017-01-31 01:48:47.209316 | Traceback (most recent call last): 2017-01-31 01:48:47.209350 | File "tempest/test.py", line 99, in wrapper 2017-01-31 01:48:47.209375 | return f(self, *func_args, **func_kwargs) 2017-01-31 01:48:47.209404 | File "tempest/api/compute/admin/test_volume_swap.py", line 64, in test_volume_swap 2017-01-31 01:48:47.209420 | volume1['id'], 'available') 2017-01-31 01:48:47.209445 | File "tempest/common/waiters.py", line 189, in wait_for_volume_status 2017-01-31 01:48:47.209465 | raise lib_exc.TimeoutException(message) 2017-01-31 01:48:47.209486 | tempest.lib.exceptions.TimeoutException: Request timed out 2017-01-31 01:48:47.209530 | Details: Volume e4fede42-0453-45b0-88c4-5285ca1fbf11 failed to reach available status (current detaching) within the required time (196 s). It looks like it's also hitting the ceph job: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Volume%5C%22%20AND%20message%3A%5C%22failed%20to%20reach%20available%20status%20(current%20detaching)%20within%20the%20required%20time%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20voting%3A1&from=7d Note that the devstack change to enable the test does not run the ceph or cells v1 job in the check queue, so we were likely not going to see the failure until AFTER the nova and devstack patches all merged. ** Affects: devstack Importance: Undecided Assignee: Matt Riedemann (mriedem) Status: In Progress ** Affects: nova Importance: High Status: Confirmed ** Tags: libvirt swap-volume volumes -- 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/1660511 Title: TestVolumeSwap.test_volume_swap fails in cells v1 job waiting for first volume to detach Status in devstack: In Progress Status in OpenStack Compute (nova): Confirmed Bug description: Ever since https://review.openstack.org/#/c/374373/ and https://review.openstack.org/#/c/399735/ merged today I've seen at least two changes in the gate get bumped out due to the swap volume test failing in the cells v1 job, seen here: http://logs.openstack.org/06/425806/8/check/gate-tempest-dsvm-cells- ubuntu-xenial/ab0bba2/console.html#_2017-01-31_01_48_47_209159 2017-01-31 01:48:47.209256 | Captured traceback: 2017-01-31 01:48:47.209267 | ~~~~~~~~~~~~~~~~~~~ 2017-01-31 01:48:47.209316 | Traceback (most recent call last): 2017-01-31 01:48:47.209350 | File "tempest/test.py", line 99, in wrapper 2017-01-31 01:48:47.209375 | return f(self, *func_args, **func_kwargs) 2017-01-31 01:48:47.209404 | File "tempest/api/compute/admin/test_volume_swap.py", line 64, in test_volume_swap 2017-01-31 01:48:47.209420 | volume1['id'], 'available') 2017-01-31 01:48:47.209445 | File "tempest/common/waiters.py", line 189, in wait_for_volume_status 2017-01-31 01:48:47.209465 | raise lib_exc.TimeoutException(message) 2017-01-31 01:48:47.209486 | tempest.lib.exceptions.TimeoutException: Request timed out 2017-01-31 01:48:47.209530 | Details: Volume e4fede42-0453-45b0-88c4-5285ca1fbf11 failed to reach available status (current detaching) within the required time (196 s). It looks like it's also hitting the ceph job: http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22Details%3A%20Volume%5C%22%20AND%20message%3A%5C%22failed%20to%20reach%20available%20status%20(current%20detaching)%20within%20the%20required%20time%5C%22%20AND%20tags%3A%5C%22console%5C%22%20AND%20voting%3A1&from=7d Note that the devstack change to enable the test does not run the ceph or cells v1 job in the check queue, so we were likely not going to see the failure until AFTER the nova and devstack patches all merged. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1660511/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
