Commit Graph

12 Commits

Author SHA1 Message Date
Ghanshyam Mann c49552281f Retire Tripleo: remove repo content
TripleO project is retiring
- https://review.opendev.org/c/openstack/governance/+/905145

this commit remove the content of this project repo

Change-Id: I235b08d63bab01a94a41b29b40724f05c88a534f
2024-02-24 11:44:21 -08:00
Marios Andreou 7b8d8ecfca Remove all rocky related config/conditionals/tests as tripleo rocky is EOL
Rocky is now EOL since [1][2] so this removes all the rocky related tests
or conditionals.
Related reviews in topic branch tripleo-ci-reduce-rocky [3].

[1] https://review.opendev.org/c/openstack/releases/+/774244
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-March/020912.html
[3] https://review.opendev.org/q/topic:tripleo-ci-reduce-rocky

Change-Id: Ibb602d1a2e3bd62463ad8861e66c23248f037923
2021-04-01 16:12:59 +03:00
Arx Cruz 9480ddcd8b Fix variable tempest_test_whitelist
The name of the variable used by os_tempest to run a specific list of
tests is tempest_test_whitelist, instead of tempest_whitelist. Usually,
we use tempest_whitelist to hold a list of tests that have conditional
to be executed, for example, if release is equal to rocky, set the
tempest_test_whitelist variable to the content of tempest_whitelist,
which is not the case here.
The undercloud-oooq job is failing because tempest is running the
default list of tests 'smoke' which have tests that are not supported to
run in the undercloud.

Change-Id: I7c264e834bd423bbe945a0c8faa4440f7e6d21f6
2021-02-01 11:08:08 +01:00
Arx Cruz c301c85f12 Replace run_tempest with use_os_tempest
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
2021-01-13 12:19:31 +01:00
Chandan Kumar (raukadah) 1f34c0df3f Added tempest_cloud_name for fs003
Since fs003 is used in older releases like rocky and queens
for undercloud deployment where clouds.yaml is not available.

Recently we moved to openstack-tempest-skiplist where we discover
deployment type based on cloud name.

In order to enable the same, we are adding this var here to detect
the deployment.

Change-Id: I85c9f1d17d7d21a75dced66dcaa726a1409d090d
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
2020-10-28 12:24:05 +00:00
Chandan Kumar aa3cecd042 Run tempest from package in non_containerized env
* In non_containerized environement, tempest should be installed
  from packages otherwise installing from container will pull tempest
  from docker.io registery which is not promoted and tested and
  resulting in failure.
* set containerized_undercloud to false in fs03 as it is non
  containerized environment.

Closes-Bug:#1800682
Change-Id: If6e70e05aca946500d40e7e703267dd934250d54
2018-11-06 13:47:46 +05:30
Alex Schultz 7ac402fcc0 Pull in instack-undercloud
For backwards compatibility on the job that runs on instack-undercloud,
we need to continue to pull in instack-undercloud and run it since we've
removed the tripleoclient integration.

Change-Id: I77ec88ad4ace718d529ef1824d82032031c4d1eb
Depends-On: https://review.openstack.org/#/c/588606/
Depends-On: https://review.openstack.org/#/c/605747/
Related-Blueprint: remove-instack-undercloud
2018-09-27 08:32:14 -06:00
Arx Cruz f11e671055 Running containerized tempest only in containerized environment
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
2018-08-10 10:08:52 +02:00
Emilien Macchi 8085fb621e Enforce use-heat=False on 3 jobs
* 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
2018-07-12 22:57:06 +00:00
Chandan Kumar f7ee860020 Run tempest on undercloud on fs003
* Added basic set of tests for running it on undercloud

Depends-On: https://review.openstack.org/560374
Change-Id: Ic4b7729d1d70ae122361d8154c81fbdb670abc53
2018-04-20 04:18:20 +00:00
Sagi Shnaidman 4aa5f03c8a Explicitly specify if to run validation in undercloud
Set pingtest and tempest to explicit values for undercloud only
job so that we can enable validation roles for undercloud and
to run only required validation - either tempest, or pingtest.

Change-Id: I8f1d350e5e74ea77191255b7b086404b1db8ff00
2018-03-13 10:16:56 +02:00
Wes Hayutin c04dc5937c break out general_config into config and topology
This change takes the overcloud_nodes variable and defines that
under config/nodes/foo.yml. This depend on the change
to quickstart-extras where a definition of topology (nodes)
will be created. Pass the topology in an explicit variable vs.
using extra_args.

The original configuration files in config/general_config/ will
continue to work but are now deprecated.
The featureset files that define standard set of feature to test are
also added, and should correspond to test configuration for jobs that
are typically found upstream

Change-Id: Id6dd3f71b33f76a0401fe8a84080fe80de0dbb69
Co-Authored-By: Gabriele Cerami <gcerami@redhat.com>
2017-03-13 13:36:13 -04:00