Ansible tripleo_auditd role is now used to configure auditd service
and puppet-auditd is deprecated and archived.
Enabling auditd service in featureset010 to test auditd service in
CI.
Currently we are enabling only for master but once the backport
merges we can enable auditd service for older releases as well.
Depends-On: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/852734
Change-Id: I4603db243eec097fcf454e6fa8367fb7a0c93d97
Job `tripleo-ci-centos-7-containers-multinode` is failing
because packaging issue in CentOS 7.
CentOS 8 ipxe-bootimgs package has:
/usr/share/ipxe/ipxe-i386.efi
/usr/share/ipxe/ipxe-snponly-x86_64.efi
/usr/share/ipxe/ipxe-x86_64.efi
CentOS 7 ipxe-bootimgs package has:
/usr/share/ipxe/ipxe-snponly-x86_64.efi
/usr/share/ipxe/ipxe.efi
So puppet in train does not set $arch for CentOS < 8, since the
packaging of ipxe.efi was not arch specific. But ipxe-snponly
is arch specific.
This change forces ipxe instead of ipxe-snponly for the CentOS 7
job.
Related-Bug: 1959726
Depends-On: Icfd03129bbb8645d4c6d64c8177fb9184ad8548a
Change-Id: Iffaee944c2a2bcfdad8dee1fe6c2c4a7a1d84155
Related change: https://review.opendev.org/806562
Would need '--baremetal-deployment' to make overcloud
deploy provision the ControlPlane VIP.
Change-Id: Ife4b15a784c70fe031af98f3aa135737232d56a6
This review adds and extra-vars to
disable protected resourced types in
releases wallaby and after for
fs010, fs037, fs035 and fs020.
There is a need to disable the resource
registry override protection to merge:
https://review.opendev.org/798642
Closes-Bug: #1943579
Change-Id: I618c0a0d99c934fb65a6af30bc76096d52d4679d
Updates the containers-multinode job to enable using ephemeral heat
using the newly added ephemeral_heat/ephemeral_heat_args variable.
Implements: blueprint ephemeral-heat-overcloud
Signed-off-by: James Slagle <jslagle@redhat.com>
Change-Id: Ide514b7f2ea94a1a82bd414840a9adb0a79ade98
This patch removes:
* legacy tripleo-validations config boolean, since now the role
is in tripleo-validations repos and is enabling by another
configuration in the zuul config directly
* documentation, because its now outdated and a new one should
be moved under tripleo-validations repos
Change-Id: Ibc5e1aec08643d53760953ebb1c026e99689a2b6
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
This removes the resource registry args for some multinode
scenarios that are currently used. There are also a bunch of
multinode scenarios that seems to have been converted to
standalone ones. They dont even have appropriate envs in tht.
Those are not changed with this patch and should be cleaned in
a separate patch.
Change-Id: Ia40bf244f91c61b8d67eadb5b00a6cade28d00b2
The overcloud deploy logs are now larger than than
the should be. Remove the verbose output to
reduce the log size.
Change-Id: Iea8f2f361013cadb048efaf3174fd18f0ecbc87c
Depends-On: https://review.opendev.org/#/c/742517/
The validations cause timeouts, we should have them tested outside of
gate/check for now.
Change-Id: I198939058b9d09b18e914db42b1bf896dc243d63
Related-Bug: #1844446
Remove *_container_cli settings out of
feature set file to single-source
the setting in tqe role extras-common.
Change-Id: I833348a18597c230fea4a01ab203569ffe5ef7a0
Depends-On: https://review.opendev.org/#/c/678881/
As overcloud clouds.yaml support landed in Tripleo for train
release and os_tempest ansible role is used for running
tempest. Multinode container job runs for other releases also
so it updates the fs010 to run os_tempest for master only.
Closes-Bug: #1837019
Change-Id: I96925574858223348faf35521fb2afdf7710e0db
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
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
This reverts commit 6822ba9a7e.
We disabled the relabeling on /run/netns, it should
work better now.
It also properly enables podman on the overcloud without extra_args,
which will avoid issues when overriding the extra args.
Depends-On: I34813b240284c8d9b35e044bc9654d556ec0cbdb
Change-Id: Id75697e86cd5d08d116d6b074342801da4572f2f
First CI job to test podman on the overcloud, instead of docker.
Depends-On: I8638386c8f394c98b047fb2ae4ff97daeeaf4475
Change-Id: Id0e737af4cb82d56b0c2db3303a767bb671917ea
Until we fix the situation, we want to remove podman from our gate.
Revert "fs010: switch undercloud to podman"
This reverts commit 39d1da5267.
Revert "fs050: upgrade the undercloud to Podman containers"
This reverts commit ab6cbcb0ce.
Revert "Switch fs027 to deploy with podman"
This reverts commit f77771843f.
Change-Id: I3715a0432ead1eb1d18deb5893858e051a0b5539
Related-Bug: #1800737
To iterate in podman testing, switch the fs010 to deploy an undercloud
with podman instead of docker, in master (stein) only.
blueprint podman-support
Change-Id: I7dd2ff456f5310735a61ee59a3e873af48260870
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
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
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/
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
This reverts commit f61f8d0e60.
tripleo-common patches aren't being tested since this merged to convert
the undercloud to containers on March 29th. Nothing updates the mistral
container to use the tripleo-common code being tested.
Change-Id: I2cb7d59ab1f42bfa6d852213b792b428a75c4fcc
Partial-Bug: #1762422
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
fs010 has too many timeouts in upstream CI, we'll stop to deploy some
services, Cinder included (already covered by 2 other scenarios).
So we want to run test_network_basic_ops instead of the boot from
volume.
Change-Id: I2a4aa707fa10664f1fc9026e3eb417f35834436f
See https://review.openstack.org/#/c/514701/ for the context.
This is a new iteration of testing config-download.
Change-Id: I18815c9920454290d965ef632a29ee13c718cd0d
Implements: ansible-config-download-ci
Depends-On: If23e223b4a0387efcc745d02154c6bdd2dee23fc
Depends-On: Iff7a1b211a545f1227b9e13e304b858128fb855b
Depends-On: I20d4107eed4c92b891e3b2dc749b8aeedfe4ef75
On FS10, use Ansible to deploy TripleO steps.
For that, it will generate Ansible configuration, download it and
execute it from the undercloud.
Depends-On: I2aa1a04ea8a963b9c613008c12b1efffd365ceaf
Change-Id: Ib7451f59664380d437a9f42efdfad09d070e8072
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
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
Enable tempest on the multinode-container job instead of pingtest.
Depends-On: I398575d565d5527bcaa1c8b33b9de2e1e0f2f6fd
Change-Id: Idf506292d38c8ee1521bc0b5cf758914d5c20ca0
Ghanshyam Mann