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
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 review adds identity.v3 (keystone) to fs16 tempest whitelist.
The TestVolumeBootPattern [1] and TestTelemetryIntegration[2] are skipped
in the master skip list meaning no tests are executed for fs16
leading to the bug below.
[1.] https://review.openstack.org/617845
[2.] https://review.openstack.org/#/c/604091/
Closes-Bug:#1803547
Change-Id: Id441fccc97c6ee7e53a9a0c22df1395b4b6368e5
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
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
* fs003: This job aims to test a non-containerized undercloud so let's make sure
heat isn't enabled.
* fs016/017: scenario 001 and 002 are timeouting. Until we figure this
out, let's make them deploying a non containerized undercloud.
Depends-On: Ibc6fb33d752346d6f8b3a61d74e0bc73c1ac20e3
Depends-On: I9ca5264b77660c34a91b051916cf17fcadf49b37
Change-Id: I7c9c016295fa28078706595dcf7c307e79b2a122
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/
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
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
* https://review.openstack.org/#/c/532773/ moves gnocchi tests
under telemetry-tempest-plugin. It is better to use and update
the name space.
* Added python-heat-tests-tempest for heat support in
telemetry-tempest-plugin
Depends-On: https://review.openstack.org/540711
Change-Id: I932721000f1954b5b1eceda9964f9313de386413
Usually, the concurrency is set to number of cpus / 2, however we are
seeing parallelism issues with this particular featureset when tests are
running in in parallel. So, let's test running the jobs without
parallelism for now.
Change-Id: I78c8b0b47595eea5d8fd417548e1f5bfeecd0889
Related-Bug: #1742936
This must be kept in sync with the archive policy configured for
Gnocchi.
See: Ie00d3487d54f4d1226f6a8a210975eabdcd8a96c
Change-Id: I62c47723d68bb1cef9733df2f737c3ab3f5aa8fb
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
Like classic scenario001, run autoscaling tests in container job so we
have test parity with the classic job.
Depends-On: Ibfeef5c557d1ceb11a999aa947597014ca94ec34
Change-Id: I4f044011f2d52148b86ebdf196c1aa949bc1e3db
Run tempest on scenario001-container like we already do on the classic
job.
It's patch on the ongoing efforts to run Tempest in our gate.
Change-Id: Ic1ab2e20a88fd33de105515cbaf5706f4a967039
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