Add a second policy to in process functional tests
Bug #1629234 reported by
Alistair Coles
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
New
|
Wishlist
|
Unassigned |
Bug Description
Some functional tests skip because they require more than one policy (e.g. tests.py:
As a bonus, if a second policy is added and it is EC, perhaps in process tests can be configured to use the second policy as the default, in the same way that encryption can be configured, and then we could have a gate job running with EC as default policy.
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/379649 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=1004509cab4 43a5cbb223ffc82 58c45cb97ee5fb
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1004509cab443a5 cbb223ffc8258c4 5cb97ee5fb
Author: Alistair Coles <email address hidden>
Date: Thu Sep 29 19:22:36 2016 +0100
Fix failing cross-policy- versioning functional test
Since [1] the functional tests for cross-policy
object versioning fails with an error. These tests are
skipped in all CI test jobs because none of them have
more than one policy enabled. However, when running
tests against a system with multiple policies the tests
will not skip and the error is raised.
[1] Related-Change: Ifebc1c3ce558b1 df9e576a58a4100 f2219dfc7e7
Related-Bug: #1629234
Change-Id: I48028928bc9962 52a31cbf3abfd2b 5e67a74dc95