The 0.5.2 version being used so far as default, has a lot of kernel bugs
that were fixed in the new version, so updating it to 0.6.2.
Change-Id: Icd7330f4f58f1815d9f5b48ffd0a80277568023b
The endpoint discovery mechanism in compute, volume, and share use
no_port_cut_url to cut the URLs after the version (including the
version) if port is not present. However, when the port is present, the
no_port_cut_url method sets the top_level to True when calling do_get
method. This causes the do_get method also cut the top_level_path of the
URLs because by default the top_level_path is set to "". This behavior
is not desired because different clouds maybe have endpoints with
different top_level_path other than "". Instead of using
no_port_cut_url, we can use utils.get_base_url to properly cut the URLs
after and including the version.
Story: #2010968
Task: #49109
Change-Id: I221b6267afce90b8b7e22d468f0824c9365f4a91
We didn't take into account that the admin role and user might be
called on with uppercase first letter - Admin - on some systems.
The patch edits the logic so that we accept this admin name or
role.
Story: #2010880
Task: #48601
Change-Id: Ie027de58f77a58f44b31274e6d75dc830d3b717d
During cloud discovery resource creation, the domain_name and
user_domain_name information used to be hard coded to 'Default' which
might not be the case for all credentials, admin or non-admin.
This patch adds support for domain_name, project_domain_name and
user_domain_name information by defaulting all of them to 'Default'
however in the case they are available in the cloud credentials, using
them during python-tempestconf runtime as well as rendering them
correctly in the final tempest configuration.
Story: 2010811
Task: 48330
Change-Id: I4355837f4d8d514524039df6f3989dbd69f2c700
We query the volume pools to check if the user has permissions to list
the backend storage, but we do not handle when the volume backend is not
available, only when the user is not allowed. This patch adds the
ServiceError exception to handle it and set the backend properly.
Change-Id: I0fd61813dbadf5ef3a0db55791e3b261d4c9d885
The commits marks several jobs as n-v to unblock the CI. The jobs
already have fixes proposed and are in the process of review.
Right now we wait on a change in Tempest which may take serveral
days to get merged.
The patch also fixes an issue with pep8 - too long line - seems
like the sensitivity of pep8 was increased because previously
the line was ok with pep8.
Change-Id: Icea222faadfe22ab029d0321fd68c3e6f1bbc0b4
Live migration supposed to work in all qemu/kvm deployment.
It is expected switch to block magrate in case of no shared storage,
tempest expected to skip migration tests when there is no multiple
compute nodes and it would lead to test failure.
Also update the documentation regarding the options set by default.
Change-Id: Id9a25ad50df85f16f27a228a0075c2e073670937
This commit changes the default value of the following option
from
CONF.auth.tempest_roles _member_
to
CONF.auth.tempest_roles member
Change-Id: Ic8263d0bfd9b093aab7f1779d24b19ca2a9b30bd
TempestConf has a set of class variables that do not need to be
class variables because there are no multiple instances of
TempestConf class that could share the value.
The reason why we need to move the class variables to instance
variables is that some unit tests under certain conditions were
failing because multiple unit tests were changing the
TempestConf.priority_sectionkeys value.
Change-Id: Ic6f51be112aa9f93904fcab289d78a7e06f20f62
When you have several controllers, if the first controller have
cinder-backup service disabled, the pacemaker return it as down, and so
the cinder-backup is set to False, even though it is running in a
different controller.
This patch do a loop to check if the cinder-backup is enabled in other
controllers, if so return it as True.
Change-Id: I3a16ec4f7b45267fcb8f9c6d01f28fe40faf7661
Since some of backends support thin_provisioning,
it's necessary to have a new parameter for skipping
the test in unsupported environments.
Change-Id: I9164a9f9d7d0dc913a1b91eb0efa741db8d523b8
python 3.6 and 3.7 are dropped (upstream tooling as e.g.
Devstack doesn't support this those anymore) together with
train and ussuri jobs.
refstack-client jobs are non-voting now until a fix on
refstack-client's side has landed. Also victoria jobs are
marked as non-voting because they require a patch on devstack's
side which isn't ready to be merged yet [1].
manila-tempest-plugin needs to be pinned in Victoria and
Wallaby because the plugin requires newer tempest version
than is available there.
The patch also makes neutron version discovery with a not
top level URL, seems like something changed because
the discovery has been failing.
[1] https://review.opendev.org/c/openstack/devstack/+/844774
Change-Id: Ia3d78e84ad9eee515eb8ca017ea84df1fd160929
The test class had hardcoded DEFAULT_IMAGE_DIR value to /img/
which resulted in unit tests failures when this path existed
because the tests expect a call to makedirs which didn't happen
as the DEFAULT_IMAGE_DIR already existed.
The patch fixes that by passing exist_ok=True to makedirs call
which will result in always calling makedirs, whether img_dir
exists or not.
Change-Id: I47d15747536394006f6b502b3025220a5077e547
Using a deployer-input file that includes object-storage-feature-enabled
section without discoverability fails, although discoverability is an
optional parameter
Change-Id: I52838fc6b6f7e576604764e1b8b7938fe4b2ea0d
If there is no public network set, python-tempestconf doesn't
set network.floating_network_name option. In order to avoid
the following error when heat_plugin options are being set:
No option 'floating_network_name' in section: 'network'
the commit adds a try except block to catch this situation
and log it for the user.
Change-Id: Ib1f04584b620fc662fd415c4430a03ea92c35b76
In case the swift's endpoint returned an exception during an
extension query, get_capabilities method returned a string of
an empty dict, which is always "true" and therefore it confues
a later if statement checking if any extensions were found.
Let's make the method return an object - dict - which will
be either true (if contains any data) or false (if it's empty).
Change-Id: Ie7974c97a4b119e41fba7150bcd2a2553300f694
Python-tempestconf assumed that swift's /info endpoint is always the
same. But it may happen that the endpoint is renamed to /swift/info
in certain situations (e.g.: when swift is on ceph).
This patch fixes the issue by trying to access the /info endpoint
first. When the connection to /info endpoint is unsuccessful then
/swift/info endpoint is used as a fallback.
Story: 43092
Change-Id: I4447e1527eae8ec75acb4fb96047c894db75620d
The assertItemsEqual method has been removed in Python 3.3 [1] but
it was kept alive by unittest2, imported by testtools. For better
compatibility, change to assertCountEqual.
[1] https://bugs.python.org/issue17866
Change-Id: Ia9768b9b889becbbc6153f3866e9fdf625fe4f5e
Due to a known libvirt issue [1], fixed in 0.5.2, we're updating the
default cirros image version. Following is from the related commit:
```
Add ahci module
Without this module it isn't possible to see any attached SATA devices
once booted, even when booting from SATA based disks.
As discussed in the associated issue the OpenStack Nova project is
looking to test the `q35` machine type that requires the use of SATA
based cdrom config drives. Including and loading this module allows
these config drives to be seen correctly within launched instances.
```
[1] https://github.com/cirros-dev/cirros/issues/64
Change-Id: Ie0d7d5ad023121c834900aac47199231b4b9af05
Older versions of tenacity doesn't support iterator in the Retrying
class, so updating the function to use the decorator instead, so we can
keep compatibility.
Change-Id: I33fa112975f355cf4f4396ec331200b15a366161
At the moment, if dashboard_url is overridden, we still try to
make a request to introspect based-off the identity URI which
isn't correct behaviour.
This patch short-circuits this entire behaviour if there's a
dashboard_url provided.
Change-Id: Ifeaec3337e5155ad1f5adeca85fce00b611a631d
Makes configuration convenient when we can
discover and set these values by default.
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Change-Id: Iecb1328f1fb3d54cfd91bb9c23d2d8ee40cf3b33
Manila's tests _need_ this configuration, and it
defaults to True. However, if there are no backends
that satisfy that condition, we need to set this
config opt to False, else tests will fail due
to misconfiguration.
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
Change-Id: I40bf6c53f205318bcd92effed433fa40f230aa02
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
A backend in manila can have multiple storage pools
and capabilities for each pool are considered to
create configuration for tempest tests. These
capabilities however may overlap with each other,
so we need some de-duplication.
Change-Id: I108615ab197b8959fe944e21ae7c1a36125ca531
Share's endpoints are versioned so we have to call
no_port_cut_url method for properly parsing the endpoint.
Change-Id: I54855f44e87a46a72da704413b1b78857858c9a7
Sometimes the image is being download from some other place rather than
the C.DEFAULT_IMAGE, and then it fails due the fact the url is down.
Add the --alt-image option allows tempestconf to instead of fail, try
again download a different image
Change-Id: Ia1af9e684dc4488841e2b54c5817902e19e51b7f
Placement's endpoints are not versioned (don't contain /<version>
in the URLs opposite to services such as compute or volume)
and therefore we don't have to call no_port_cut_url or do_get
method *with* top_level set to True whose take care of cutting
the URls after the version (including the version).
python-tempestconf is able to discover the endpoint and as it's
not versioned, we don't need to do any further processing.
Story: 2008679
Task: 41980
Change-Id: Id3c270fa4a0b09c19edf6c0c9dba48a2235d1907
The patch adds the abbility to automatically set
CONF.dashboard.disable_ssl_certificate_validation for
horizon service.
Change-Id: If23bd0973d0bd63f3e265ef615904df7931dc2ff
Deprecated scenario image options are being removed from tempest,
see [1]. The tempest change makes img_dir obsolete
therefore CONF.scenario.img_file needs to contain the full path to
the image now.
CONF.scenario.img_dir will be removed entirely from tempest in the
near future by [2].
[1] https://review.opendev.org/c/openstack/tempest/+/710996
[2] https://review.opendev.org/c/openstack/tempest/+/754927
Change-Id: Icf7ac92807873d0a5cd8ccaf75033003adb21c0a
Some tempest tests require placement service microversions to be
specified, e.g. MinBwAllocationPlacementTest. This patch adds
discovery of the placement service min and max microversions.
Change-Id: I639cbf0d63cc2a3235615762d61347b9bb0c5e6f
Started by Rocky release
* ``CONF.volume-feature-enabled.api_v2``
* ``CONF.volume-feature-enabled.api_v3``
are deprecated and have no effect.
``CONF.volume.catalog_type`` will be used instead.
Volume APIs tests have been moved to v3 as default and can be run
under v2 API via catalog_type.
- https://review.opendev.org/#/q/topic:volume-default-testing-v3+(status:open+OR+status:merged)
Story: 2007283
Task: 38735
Change-Id: Ia4c07bdda484828a29e9bfa299134f69d0f4050a
Arx Cruz
yatinkarel