delta/openstack/python-openstackclient.git/openstackclient/tests/functional/compute/v2/test_aggregate.py, branch 5.6.0

Refactor AggregateTests

2019-11-05T21:32:15+00:00

While investigating the referenced story/bug I noticed that
wait_for_status in
openstackclient.tests.functional.compute.v2.test_aggregate.AggregateTests
was doing a lot more than it should ever need to (it probably got copied
in from somewhere). The two places calling it only need to a) check the
output of `openstack aggregate show`, and b) try once -- since they just
got done creating the aggregate synchronously, there should never be a
need to delay/retry. So this commit removes the helper method and just
inlines the check.

At the same time, the addCleanup(aggregate delete) directives are moved
above their respective creates. This is a defensive best practice which
makes sure cleanup happens even if something fails very soon after the
actual back-end create (as was in fact the case with the referenced
bug/story).

It is unknown whether this will impact the referenced bug.

Change-Id: I0d7432f13642fbccd5ca79da9c76adfcbabb5fa9
Story: 2006811
Related-Bug: #1851391

More aggregate functional race chasing

2019-09-10T19:09:29+00:00

AggregateTests.wait_for_status() was a classmethod, those often
are sources of conflict in parallel testing...

Change-Id: I6211fd9c36926ca97de51a11923933d4d9d2dfda
Signed-off-by: Dean Troyer

Format aggregate command fields and de-race functional tests

2019-08-26T22:50:06+00:00

Rename metadata to property in all aggregate commands

Beef up functional tests to reduce street racing

Change-Id: I4598da73b85a954f3e6a3981db21891b45d9548c
Signed-off-by: Dean Troyer

Serialize more aggregate functional tests

2019-05-18T00:15:28+00:00

These tests are showing signs of problems running in parallel
so serialse the create/delete/list/set/unset tests.  They all
used two aggregates each anyway...

Change-Id: Iba4b52c179e6914eaeefea1da0f7eaefcdcf1f87
Signed-off-by: Dean Troyer

Aggregate functional test tweak

2019-05-16T12:43:55+00:00

This seems to still be racy, lengthen the timeout to wait for
agregate creation.

Change-Id: I3601c5baee03745ae21714b9dff0e278ad016877
Signed-off-by: Dean Troyer

Slow down and retry aggregate create/delete to lessen race

2018-07-06T18:15:59+00:00

Change-Id: I676894c1bfd3156313d88e6457250b9ff226118b
Signed-off-by: Dean Troyer

Attempt to work around chronically failing server issues with aggregates and qos

2017-09-15T17:34:15+00:00

So yeah, this is not kosher for functional tests, but we're testing the
client interaction, not the raciness of Nova or Neutron.  Failure to delete
is not our problem.

Change-Id: I21043f1de0fbacee1aec63110fb12a7cff42e0a0

Nova-net functional tests: aggregates

2017-05-02T19:09:16+00:00

Nova-net requires a cells v1 configuration to run as of Ocata, but
aggregates and cells v1 are not golfing buddies, so don't let them
meet on the back nine.

Skip the aggregate add/remove host commands in the cells v1 config,
leave the others because they should work, just not be very useful.

And format things consistently.

Change-Id: I131d9f883cb7aca53ad82fb7d5fc6ee1c1e7d923

Functional test for aggregate

2016-11-27T18:32:48+00:00

Using json format output in aggregate functional tests.
Remove resource create/delete from setupClass() and
teardownClass() methods

Change-Id: I6494ca63bfe8a51de0f65570fddcaf38f6c42dbb

Update functional test for aggregate.

2017-01-16T20:58:33+00:00

Add the following functional tests :
    option: "--no-property"
    command: "aggregate set --zone",
             "aggregate add host",
             "aggregate remove host".

Change-Id: Ia9c31facb5f0f5b92b8df950fd4021b8ecc924c5