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
The variable run_tempest was used by validate-tempest. Since now we use
only os_tempest, this variable is no longer required, however, since
use_os_tempest is default to true, we must change it where the
run_tempest is false, like in the upgrade/update jobs, since we don't
run tempest on those.
Change-Id: Idb8166992976ce6303f95f72011aa65fe536931e
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
The bootstrap environments for deployed-server were deprecated in
I95f43da44c869f5de2fa4cdaa3d07fcef4ef11b9 are no longer required as the
bootstrap tasks were migrated to tripleo-ansible in train.
Change-Id: I18505b14353d26914e95152a253d19583ef4b48f
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
- Enable containerized undercloud for 3nodes jobs, it's ready to work.
- Disable containerized undercloud for upgrade job, we have some THT
mismatch in quickstart, and we need to fix it. In the meantime, make
sure we don't deploy it.
Change-Id: I910b15f78dc5a10e304d5aaf249516c56c82f6d0
We incorrectly dropped the config download items in
Ic5c5df350a7eb5291d45cf8e229af575fe9bed57 for featuresets that had it
enabled in queens. Since we won't be backporting the default changes in
tripleoclient back to queens we need to add a special case for these
featuresets in queens.
Change-Id: I9aa449a3198568c25d4dbc838669f493b0e3c103
Closes-Bug: #1771549
Now that config-download is the default across tripleoclient and
tripleo-heat-templates, we can update all the CI jobs to remove the
explicit --config-download and -e
environments/config-download-environment.yaml.
Note that --deployed-server didn't actually trigger any needed behaviors
with --config-download, so where it was used, it has now been removed as
well.
Change-Id: Ic5c5df350a7eb5291d45cf8e229af575fe9bed57
* 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
Enable config-download on fs032 (multinode-3nodes), so we can start
testing config-download with custom roles in TripleO CI.
Depends-On: Ia13b3adf91324bb96cd13281c7469412734e151b
Change-Id: I9829845b83bd43e1d66f6be010369dde8ef47b5a
--overcloud-ssh-user is needed on multinode jobs.
Since 3nodes-multinode override multinode_args, we need to keep the same
arguments needed from:
9449198547/roles/overcloud-deploy/tasks/pre-deploy.yml (L205-L210)
Change-Id: I7b25cac1f13067832374dba2023fdc8044cc5587
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
This add featureset032 to allow us to move the current 3nodes
multinode job to run via quickstart. This allows for HA testing
on deployed servers, as it will deploy 2 controller nodes and
enables pacemaker.
Change-Id: I7fd723b5547896693e57c76415ab98b98abfdcfc
Ghanshyam Mann