[openstack-dev] [gate] [cinder] A current major cause for gate failure - cinder backups
xiaoyan.li at intel.com
Wed Aug 24 07:24:54 UTC 2016
I noticed that as VolumesBackupsV1Test and VolumesBackupsV2Test use same volume to do backup creation test etc.
When creating backup from volume, it needs to attach volume. As both two tests use same volume, they attach the volume at same time, and leads failure.
I opened a bug https://bugs.launchpad.net/tempest/+bug/1616338, and will fix it.
From: Sean Dague [mailto:sean at dague.net]
Sent: Wednesday, August 24, 2016 10:21 AM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Subject: [openstack-dev] [gate] [cinder] A current major cause for gate failure - cinder backups
The gate is in a bad state, as people may have noticed. We're only at a 50% characterization for integrated-gate right now - http://status.openstack.org/elastic-recheck/data/integrated_gate.html
which means there are a lot of unknown bugs in there.
Spot checking one job - gate-tempest-dsvm-postgres-full-ubuntu-xenial -
6 of the 7 fails were failure of cinder backup -
- though they were often different tests.
With the current state of privsep logging (hundreds of lines at warn
level) it is making it difficult for me to narrow this down further. I do suspect this might be another concurrency shake out from os-brick, so it probably needs folks familiar to go through logs with a fine toothed comb to get to root cause. If anyone can jump on that, it would be great.
This is probably not the only big new issue, but it seems like a pretty concrete one that solving would help drop out merge window (which is 16 hours).
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev