This change removes logic for releases older than train, because these
releases are already EOLed. This covers only tempest roles and
playbooks.
Change-Id: I0b50cad30107a83b562b8c22b2afd7af7636c615
This template was using the old yaml file, since we still have some jobs
running validate-tempest, and the skiplist files were already
deprecated, we need to load the testes from the new tempest-skiplist
tool.
Closes-Bug: #1899980
Change-Id: I954edaf6de84d97dd896b6bbb092931122740b9c
There was an absence of ResellerAdmin role in
the configure-tempest.sh.j2
This patch fixes it.
Related-Bug: #1862143
Signed-off by: Soniya Vyas<svyas@redhat.com>
Change-Id: I34b76c70986da82fde8c74cbbcfd7a5d55ea9405
In Rocky and Queens tempest contains a default value for nova scheduler
filters equal to all, which results in the mentioned bug when tests which
are meant to be executed against specific filters are not enabled in the
system.
Overriding filters in tempest to only those which are available in the system
will skip the tests which are meant for different filters.
Change-Id: I98532113d3ad1339fdc4869686ad875b304f094e
Closes-bug: 1857365
To prevent cleanups of the octavia network resources that are created in
the overcloud during deployment.
Change-Id: Iff54ff52c9db65e3675af69fc17dd9461eb596a5
https://review.opendev.org/#/c/676439 added this setting to
fs001 but it's needed generally. Adding it to
configure-tempest.sh.
Change-Id: Ic23fb25f1d03d35edd4ae8850003b90db422b438
Related-Bug: #1836046
As https://review.opendev.org/#/c/638617/ takes cares for looking
for Member role so we do not need to specifically specify the same
in tempest config extra overrides.
Depends-On: https://review.opendev.org/#/c/660060/
Closes-Bug: #1828859
Change-Id: I478e5f036e3c57c09dae6623bf00e4b4f40e55cb
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
https://review.openstack.org/#/c/645500/ with this review
if heat is enabled, tempestconf tries to set the conf for
heat tempest plugin where regionOne is required but in
stackrc It is missing which leads to failure for
generating tempest.conf.
Closes-Bug: #1825265
Change-Id: Id7dd0c0902536226aa9874a41407baef2f21f821
Signed-off-by: Chandan Kumar <chkumar@redhat.com>
We weren't testing containerized tempest in standalone job due the
missing logic on tempest-setup.sh script. This patch adds the logic for
when containerized tempest runs in standalone, copying the clouds.yaml
file instead of the stackrc/undercloudrc and also maintain the logic
when you execute tempest in the ovb, copying the rc file.
This also ensures that /var/lib/tempestdata and /var/log/tempest
directories exists in order to not fail the execution of containerized
tempest.
https://tree.taiga.io/project/tripleo-ci-board/issue/836
Depends-On: https://review.openstack.org/#/c/643212/
Change-Id: I90204150085a1c9b943f9e054c0420a8a5e66538
Related-Bug: 1819440
Currently when podman tempest container tempest tests fails, it
stores the exit status as fail and exit the run_tempest.sh script
leading to not copying the stuff from tempest container to host.
It decouples the step of copying and managing permission for tempest
post log processing and run only when tempest run finishes with in
a container.
https://tree.taiga.io/project/tripleo-ci-board/task/819
Change-Id: I9c7f97f3aa97c0ea061ba6aeb125501bf3a1adbf
In order to run novajoin tempest tests for testing tls in tempest
container we need to mount ipa related files and export
KRB5_CLIENT_KTNAME within tempest container so that novajoin
tempest plugin ipaclient can access those and help to run tempest
tests.
Copy tls related files in pre-tempest phase.
https://tree.taiga.io/project/tripleo-ci-board/us/670
Change-Id: I105d7839a3cdbf6e69d006fc588fb7d13e4e3a03
Let's make it obvious if tempest is executing
via the container and not from the undercloud.
echo out a statement, noting it.
Change-Id: I50a6b8ebcf33a7d216237b06f1e3e24867d17f58
https://review.openstack.org/#/c/608452/ Switch the undercloud to
deploy Podman by default starting from Stein and
undercloud_container_cli var is setted under undercloud_deploy role
and it cannot be used in another role which will set
container_binary to docker but docker is not there in stein leading
to fail running tempest from container.
Use sudo while pulling tempest using podman
Change-Id: I7ee75d71a7c34bdb85232a1378880ff16579c5db
Related-Bug: #1816026
Set up resources on the overcloud so that ironic
can be used to deploy baremetal.
- Add IPA deploy kernel/ramdisk image
- Add a cirros wholedisk image
- Create a provisioning network
- Adds baremetal nodes
- Updates the flavor user by ironic
Change-Id: I1dc1f121b937f73d89d3f1ae8511f36cb526b2a8
In order to use it, in any FS, set tempest_format to venv
and then set:
tempest_plugins_venv:
- '<complete upstream openstack tempest plugin git url>'
Change-Id: I95a4449ca3976a914faf1ba5f3f4c0e756a6fefc
* While porting the validate-tempest to podman[1], we added tempest_data
variable to keep tempest related input data files while running in
container, All the dir path in the script got updated but tripleo
deployer input path was left to tempest_dir but we were keeping
the files in tempest_data dir due to which tripleo deployer
input file was not passed leading to the failure of object
storage tests.
[1.] https://review.openstack.org/605356
Change-Id: I132009d3f00bb4bcff3b21def0edd568bfab14ec
Closes-Bug:#1773325
Simplify the logic in jinja to more explicitly
create the tempest skip list. There are three
different types of deployments for tempest and
it should be more clear how the skip is generated.
Closes-Bug: #1803419
Change-Id: Iade08ee92d7f48e07a625678d2a1c6ac1cd1982b
* https://review.openstack.org/#/c/600517 introduces undercloud_container_cli
to choose docker/podman container runtime. This changes introduces to use
both docker/podman for running tempest tests.
* Tempest user does not have permission to create tempest workspace let's
create the tempest workspace and own it with the tempest user.
* Introducing tempest_data directory to keep tempest related data
which can be used by tempestconf and tempest run to tests
* Cleaned up stuff which is not necessary for tempest container.
Depends-On: https://review.openstack.org/#/c/614664/
Change-Id: I1b19b2580d1d4c9844e9221f18b23655b36b5a23
* In order to run full tempest tests, we need a public network which
can be consumed by tempest tests in order to run full tempest tests.
Change-Id: Ib643dba40efa49095715fcf17f93894ebc8cdea9
Since the standalone deployment uses clouds.yaml, we need the validate
tempest role to allow for configuration using OS_CLOUD rather than the
traditional {stack,overcloud}rc files.
Change-Id: Ied55638618b718ee15a2ef5bc2f89cef232b5b7e
Related-Blueprint: all-in-one
Rerun of tempest-setup.sh was broken with containerized
tempest. tempest_container.sh was appended with rerun,
this patch fixes it by creating a new tempest_container.sh.
Closes-Bug: #1784555
Change-Id: I496b33ba3579985b5ba72286c066b0c102dcdd17
* https://review.openstack.org/592276 marks the release of tempest-
19.0.0. Let's update the role to consume it
* Updated skiplist for rocky
Change-Id: I7a758d740d20ef8036d301aa612184186bac62f0
The python-tempestconf uses requests python module to make the calls to
the openstack api, if ssl is enabled, the requests throws an error
saying that cannot validate the certificate, and so fails. This only
happens when we run tempest containerized.
In order to avoid that, we are using PYTHONWARNINGS and CURL_CA_BUNDLE
environment variables to skip ssl check.
Change-Id: Id53643fecc545a2a15b8bab478dd49d32de4068c
* Shell commands are not interpreted in single quotes and
this patch fixes it.
* It also remove tempest_data dir created in previous tempest
container run to fix dir exists
Change-Id: I6af87d5013c8311eb36ebddf947bd921c6fe13f0
* https://review.openstack.org/#/c/583940/ added tempest user with
tempest container to fix tempest init log issue and it broke the
container as all the directory with in tempest container and files
getting mounted from host have different permision. It fixes the
same.
* It moves all the tempest related files to tempest_data dir and then
mount the same to tempest container by changing dir permission if
tempest user is present else run the docker run as it is.
* Moving tempest dir creation step under container shell script
Change-Id: I9696b490e5d4646044de5258c676a357ee2779bb
Closes-Bug: #1783055
Depends-On: I20f04e8b821058a89a5464c9be1bb14d30f1f223
Tempest containerized run as root, and so, although the
tempest-deployer-input.conf file was being imported to the container,
the patch was ~/tempest-deployer-input.conf that was pointing to /root
instead of working_dir, so, tempestconf wasn't getting the defaults from
the deployer input file, setting the region to RegionOne instead of
regionOne, and so, the object_store tests were failing, because was
getting the default endpoint http://.../ instead of http://.../v1/AUTH
Change-Id: Ic88c9121441b4021da3400933cacc4ff942b727f
Closes-Bug: 1773325
* It changes the git url of python-tempestconf and tempest
and list files to make sure directory get clonned.
Change-Id: I82ea378ac5da93e65db44613404965566903a89f
With the right envs "Create overcloud tempest setup script" task fails
with "AnsibleUndefinedVariable: 'dict object' has no attribute 'iteritems'"
this changes moves that for dict.items().
Change-Id: I23ebc34f538f6be3bc271f101a32ed8121710a5f
Since the certificate is not validated in tq/tqe, and tempest default is
to enable the validation, adding it for override. There are some
featuresets already failing due this.
Closes-Bug: 1779628
Change-Id: I5a5ddda04d1cddb1c712ac79e8b78a0faaa57a9f
Review [1] removed tempest config for all releases but
the patch [2] that added these parameters in python-tempestconf
is currently available only in rocky.
This patch fixes this param for older releases unless there
is plan to use the tempestconf patch in older releases as well.
[1] https://review.openstack.org/#/c/570159/
[2] https://review.openstack.org/#/c/570157/
Closes-Bug: #1779271
Change-Id: Id30e9cc7b237e09486c72d9fe2c1354814a3b993
The following options are being handled now by python-tempestconf
* compute-feature-enabled.attach_encrypted_volume
* compute-feature-enabled.console_output
So, this is no longer required.
Change-Id: I5c3f1e008d6a9c4fa53a2c085039255f41a059ee
Ghanshyam Mann
yatin