This reverts commit 73bab8395b, reversing
changes made to c165c42c00.
This change introduced a new test under an existing test class, which
is a breaking change and prevents us to keep testing older releases.
This new test will be soon re-introduced under a new test class.
The biggest change is that the upgrade_groups() is a list of tuples ...
[()] ... rathern than a collections.OrderedDict(). This tends to make
more sense as they are processed in order and don't actually need to be
indexed.
Also excludes easyrsa (as it's not an upgrade target) and adds a
"Database Services" which upgrades mysql or percona FIRST before moving
on to rabbitmq and other stateful services. This is because some charms
really need to talk to mysql if one of the other stateful services does
a relation changed hook. This makes it more likely that the system will
ugprade correctly.
* Use juju model as workspace and store in home
The current juju model will now be used as the tempest workspace name.
Additionally, all workspaces will be stored in ~/.tempest/<workspace>.
This patch also introduces a new option 'keep-workspace' that can be
specified along with other tempest options to keep the workspace after
tempest test execution. It defaults to False.
Also minor adjustment to smoke option to test boolean value.
SAML Mellon tests have been broken on Focal. The handling of the region
selection behaves differently from bionic. Or it may be that bionic
accidentally was working by seeing a string as int 0.
Horizon has a "default" region which returns the keystone URL.
A recent change to allow multiple zazas to run at the same time fixed
the cacert file into a local 'tests/' directory. Unfortunately, that
doesn't exist for every environment where zaza runs (e.g. mojo) and so
this patch ensures that the path exists prior to trying to download into
it.
When creating an Arista-backed Neutron network, the API call from Neutron
to Arista sometimes spuriously fails. This is not fatal and Neutron
simply retries a few seconds later. The tests now account for that.
Add a ceph_ready config step which just checks that the ceph units
are in a 'active' 'Unit is Ready.*' state. This is useful when
encryption at rest is being used and the tests.yaml assumes that
the units are going to come up blocked. Once vault is ready the
tests then need to wait for the ceph units to become unblocked.
