Since we are working in process of removing tempest container
from wallaby release and all the tempest run is switched to
os_tempest for all supported release in tripleo-ci.
This change is not going to affect any periodic jobs also.
It also removes run_tempest and tempest_format var.
Related-Bug: #1916875
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I3d046047833044fd2d75ba399f784be5d992fbef
Removes the redundant undercloud mapping from featuresets.
We've the default mapping in environments/undercloud.yaml.
Also this CI specific environment is redundant.
Change-Id: I72e41fb8cdebff12aab9704c2a9c4e368410c1ad
This normalizes the formatting of files from ci-scripts and config
folders in order to allow further hardening of linting.
Fixing linting was too big to be made in a single commit as it would
involve too many files to review and could merge conflicts with
existing changes. Thus doing it in few chunks would makes it possible.
Original full change is at https://review.openstack.org/#/c/627545/ and
will be the one merging the last.
Change-Id: Ifb215c0e2ea0ef7115897721f75ba8489bd59b97
The bugfix to manila's tempest tests
has merged [1]. Only enable them in pike,
until test issues have been fixed in ocata.
(Newton's EOL upstream).
Also cleanup the manila API version switches
for readability, and tag the appropriate version
of the manila test package in featureset008.
[1] https://review.openstack.org/#/c/603171/
Closes-Bug: #1790857
Change-Id: Ia0418fa210f13392643c3b960a8baeec7c168304
Manila's tempest plugin has a critical bugfix [1]
that needs to be applied to the "python-manila-tests"
package in pike, ocata and newton.
While we fix that up (LP 1790857), we can disable
these breaking tests as a temporary workaround to
unblock promotions.
Related-Bug: #1790857
[1] https://bugs.launchpad.net/manila/+bug/1743472
Change-Id: Ia19ee3381d8560b79e04bb7814174faf88b43a36
* The package name for manila-tempest-plugin for pike is
python-manila-tests and from queens onward it is
python2-manila-tests-tempest
Change-Id: I285cbe7b3d17a395ed6b574ad5bcac71c219a71f
Related-Bug: #1790857
Manila's API is versioned, and each release
has a different version maximum that we want
to test with.
Change-Id: I51b799cd2adf2c38cb93727552ae750cc4d9bead
Closes-Bug: #1790857
In queens, the ceph-ansible workflow does not work with config download.
These jobs should not be using config-download. This was improperly
converted as part of I881f92e6cef4de58a9731f03669e42bc862964ec. This is
a partial revert of that patch for featureset016 and featureset019. The
featureset documentation indicates that these are not configured with
config download.
https://docs.openstack.org/tripleo-quickstart/latest/feature-configuration.html
Change-Id: Ib6c3ca7886c5e4adb0883c501bfbb390e15d108f
Closes-Bug: #1790144
Related-Bug: #1789416
The scenario based deployments were not updated properly
for config download.
Closes-Bug: #1789416
Change-Id: I881f92e6cef4de58a9731f03669e42bc862964ec
When tempest is enabled and one of scenario004*, which include
Manila, is used, install the Tempest plugin for Manila and add
a representative test and the related configuration (thanks Tom,
Raissa, Dustin and Goutham).
Also, reformat tempest_extra_config as multiline as much as possible.
Depends-On: https://review.openstack.org/540070
Change-Id: Ic365519bd83ab1da509d1d66aa440a9c0a0ed5a0
Tempest container is available and built when we deploy
containerized undercloud.
Since undercloud is containerized from rocky and ongoing, this patch
enable containerized tempest when undercloud is running as container.
Also, moved all tempest related configuration to the end of file to
avoid overwritten options
Depends-On: https://review.openstack.org/#/c/580384/
Change-Id: Icdb0f2b033ad0d1ba2548c591fa32dc649fff319
* https://review.openstack.org/568869 implements using swift
healthcheck api to discover swift services and set the
tempest.conf based on that.
Change-Id: I145a8212af53c3ed98ca04c316a980d8aea8ab29
Bug was introduced in https://review.openstack.org/#/c/566527/
Set default value for tempest_format in logs collection role
when it publishes docs.
Closes-Bug: #1776164
Change-Id: I25a73bbd3804cf013f38627ca3d742e3a6a2f5d1
From master and onwards, we are going to run tempest in containers.
This set the following jobs to run tempest in containers:
* tripleo-ci-centos-7-containers-multinode
* tripleo-ci-centos-7-scenario001-multinode-oooq-container
* tripleo-ci-centos-7-scenario002-multinode-oooq-container
* tripleo-ci-centos-7-scenario003-multinode-oooq-container
* tripleo-ci-centos-7-scenario004-multinode-oooq-container
* tripleo-ci-centos-7-scenario007-multinode-oooq-container
Change-Id: I3af9ad4f43c1c056bd732124eaf4f1f6f194be5b
Depends-On: https://review.openstack.org/#/c/562155/
* https://review.openstack.org/551441 introduced test_black_regex
in order to skip test directly from featureset files. In order
to avoid confusion between test_regex and test_black_regex, we
are renaming test_regex to test_white_regex.
* It will fix all the featuresets.
Depends-On: https://review.openstack.org/560006
Change-Id: If66225c2e2f8c571cc85aebacee01431e4f64dcc
Once workflow_tasks are removed from the ceph templates, we no longer
need to include the environment to explicitly disable them.
Change-Id: I3f2efc62e29694882ffa0d950056151fc8bef563
Depends-On: Ib7851e02424d4adb1490e8ed36327dc4a573c44f
Use config-download in the scenario jobs that deploy ceph so we can test
ceph-ansible with external_deploy_tasks.
Implements: blueprint ceph-ansible-external-deploy-tasks
Depends-On: I4b88e97c38ff394023a92bec5631b3cd0f6e293e
Change-Id: I757be222143e41392b474d6b20c7a7b7df4537de
deployed_server is no longer common
through out the multinode featuresets.
deploy_steps_ansible_workflow is an
alternative now.
Related-Bug: #1748315
Change-Id: I28988d30338527669da25bc764143cf57a995af9
We don't have swift on scenario004, but Ceph RGW.
This patch is a technical debt, python-tempestconf should be smart
enough to know that Swift isn't actually enabled in the deployment even
if there is an object service in Keystone catalog.
It will be fixed in tempestconf, but in the meantime here to get a
promotion in CIs.
Change-Id: I512b7956dfe070e46ad2c7201f4ccad6e5024f48
Related-Bug: #1725311
Use the new upgrade_composable_scenario variable from oooq-extra to set
the composable scenario file used during upgrade.
Closes-Bug: #1714905
Change-Id: Ie0e8de54794a9259c0aeb8c67ae0f6a908844093
Adding the docker registry config to the featureset config
breaks the fs config when executed in other environments.
Depends-On: I9b3ac36033c0b9e994a13188f750e9e1d484bd2d
Change-Id: I5b8a99b4ada9868169a4631aa591a911357f9bcb
enable pingtest where we know it works, scenario001 and 003 for now.
002 and 004 will follow soon.
Depends-On: Idbd02a3c7404daecdc6e2c45ea6d3478bf70552c
Change-Id: Ic363a0629fa36397638b4d617007783a1e2f7dc8
This configuration was previously in tripleo-ci in the
testenv/multinode.yml file, but it is not specific to tripleo-ci.
This would be nice to add to the common multinode config and only
override where needed, but our current code does not allow for
overriding what is in the common config.
Change-Id: Ia042fc578ade2c073504ceb117b1da3ff0a4e051
The "deploy_composable_scenario: true" variable was missing from our
scenario based featuresets, which was masked by an override in our
upstream testing, but results in missing the scenario files when trying
to reproduce them with the featureset configs only.
Change-Id: I7e7c13b9151607233f1159ed91c455dcec37e230
Ghanshyam Mann