The job was failing because of a bug described in the launchpad [1].
As this bug is resolved and the job is no longer failing we can
start using this job again.
Before enabling the devstack-admin-plugins job we need to fix two
things:
- Put test_manually_trigger_update_secondary_zone_negative designate
plugin test to exclude_regex as it is currently broken.
- Allow git to read plugins directories. This is necessary because
of a patch that was recently added to git [2].
[1] https://bugs.launchpad.net/neutron/+bug/1959125
[2] 8959555cee
Change-Id: I5bf3826f0011a9392a38ceceb51c113d38231ad6
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
Some changes have been merged to python-manilaclient recently
which aren't packaged yet and therefore cause problems in our
gates - the jobs are failing to create a share group type.
Installing the client from source will fix our gates.
Change-Id: Ia4d856118fa204f821c3ec0fdf39d210eaad34b1
Let's activate a few jobs which were commented out in order to
unblock the gates and merge necessary changes.
Change-Id: I07b923d48aab5908c48fcfdd3a3fb23207178be7
Publishing documentation (including release notes) to docs.openstack.org
is not expected from non openstack/* projects.
This patch ensures that release notes are published to docs.opendev.org
together with tempestconf documentation.
Merging of the release notes with tempestconf documentation is
done using symlink created in the docs/source folder.
Change-Id: I042305f7fdbceb576d7e8d41297111f11caced99
The documentation of tempestconf should be published to opendev.org
instead of openstack.org because openinfra/ projects are not expected
to publish docs to openstack.org
Change-Id: Id4f76a5ac5ac1fa01beacd981fc8e9e93b567a3a
Lately osf/ namespace got renamed to openinfra/ [1], this commit
reflects this change within python-tempestconf's repo.
A few jobs are temporarily put to non voting or disabled (due to
taking long time to finish or due to failures) to unblock the
gates.
[1] https://review.opendev.org/c/openstack/project-config/+/808479
Change-Id: Iecc81881f5d541e0114e880e4b5326c1c064ea09
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
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ide03d00b0def455b49de032c69a486a7a1ba1574
As we have created a new tag (3.2.0) let's create a new
releasenotes section in order to present the changes done
in the latest release.
Change-Id: I266d27c3fc9216ddbae87c6fe69ca0fccd4ed265
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
To follow tempest's change [1] regarding the inclusive jargon,
the patch renames arguments for tempest zuul jobs.
Also a tox version is bumped so that we can use the newer
tox options.
[1] https://review.opendev.org/c/openstack/tempest/+/768583
Change-Id: Ifa0ae749904093810d95af2ec8e006e1cce20f86
Let's skip test_create_update_server_with_subnet from
heat_tempest_plugin because it is constantly failing on a timeout
issue:
'failed to reach UPDATE_COMPLETE status within the required time
(1200 s)'
The test is working locally so the failure is not caused by any
tempestconf's recent change or by a tempest.conf issue in general.
In order to unblock tempestconf's CI, the patch excludes the test
in python-tempestconf-tempest-devstack-admin-plugins job.
Change-Id: If9f9b3be758897f25d16326aa6d0f7c53e110122
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