There are no longer imports from the train branch.
This review remove Train from check/gate templates.
Change-Id: Ie24ab5b5b16d8a6af4f7d37483367f60265ee1ab
Add content provider job, which builds containers using `current` dlrn
tag on same release branch as regular content-provider job.
Apart from new content provider job, the change adds new variable called
`minor_update`, which enables to consume containers created by new
content provider job in depended multinode-oooq-container-updates job.
minor_update variable is used in featureset068.
The featureset is activated in jobs for wallaby branch and onwards.
Train job uses featureset038 as previously.
Related-Bug: #2015993
Change-Id: I7a7713be0cd15321d5b16f6b8ca85f06d296219f
Re-use the multi-rhel deployment (fs 66) and add the update variables
to the new job.
Use the run_test_role_vars to pass the variable to the role.
Change-Id: Ica24513c6542376695d6c2f5d71e57166b0aca3f
It seems flake8 is no longer available in Gitlab. This change switches
the source from Gitlab to Github to avoid the following failure.
fatal: could not read Username for 'https://gitlab.com': No such device
or address
This also makes sure that functional jobs are skipped when pre commit
config is changed, to avoid the failing job graph freeze when updating
only .pre-commit-config.yaml.
Closes-Bug: #1996668
Change-Id: I79143651e432cb4a62dafdb94c839d0d782b4f9f
Also fixes gate issue in deprecated layouts using the 'old'
queue syntax per the change at [1]
This reverts commit a860a16e93 and
fixes deprecated queue syntax
[1] https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030505.html
Reason for revert: See discussion in Related-Bug job is now green again
Change-Id: Ic9fa83f612604dc15401b6f5694326459487d8fe
Related-Bug: 1989341
The scripts directory in tripleo-common has a few core script files
like bootstrap_host_exec and any change with these scripts should
trigger actual deployment jobs.
Change-Id: I2405ba227b39ad1bd81baf40031edb55dcf06429
Codes under the test directory are not used by actual functionality but
only by unit tests. Thus we don't need to run functional jobs in case
only these test codes are updated.
Change-Id: I425c111238768163ed237d57e16c68f391b0f41c
Includes changes to pass the registry_distro var through to the toci
playbook executions. Also adds the registry_ip_address_distro and
_hash_distro into the content provider return data for use by the
mixed-os-job. See topic at [1] for related reviews.
The new job is in the tripleo-multinode-container-minimal-pipeline
layout so it will run across the tripleo repos (wallaby only).
[1] https://review.opendev.org/q/topic:oooci_mixed_rhel
Change-Id: I1690fbece3ef8d40cef01ef0d10f5f5edbfe2747
Any change in molecule test files does not affect functionality. Thus
there is no need to run jobs which involves deployment if only the test
files are updated.
Change-Id: Ia5cfbee55f094486eaed9f5fd51316654b57025b
Removes any job definitions that are wired up for old EOL releases.
In some cases just remove these from the branches: match.
Depends-On is needed for standalone/scen3 used in sahara and
centos-7-standalone-os-tempest in ansible-role-python_venv_build
and scenario001/2-multinode-oooq-container in aodh
Change-Id: I946aaef1e975bb2817311059dade029fadba9b95
https://opendev.org/openstack/tripleo-ci/src/branch/master/zuul.d/base-upstream.yaml#L92
adds ^setup.*$ under irrelevant-files and content-provider is parent
from tripleo-ci-base-standalone-standard and which parents from
tripleo-ci-base-standard.
Since setup.* files under irrelevant files so content provider will
not run and undercloud, upgrade and standalone job depends on that.
It leads to job freeze issue. Putting setup files under
irrelevant files fixes the issue.
Disable auto discovery as a workaround to fix
setuptools 61.0 issue[1]
[1]. https://github.com/pypa/setuptools/issues/3197
Related-Bug: #1966382
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I43b88e356e1f6823f9febe47e9753cf3e5b176c6
Based on CS job parenting re-structure[1], for multinode jobs,
It follows the following inheritance
* tripleo-ci-base-common-required-projects
* tripleo-ci-base
* tripleo-ci-base-multinode-standard
* tripleo-ci-base-required-projects-multinode-upstream
For Distro specific
* CentOS 7
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode
* CentOS 8
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode-centos-8
* CentOS 9
tripleo-ci-base-required-projects-multinode-upstream
- tripleo-ci-base-multinode-centos-9
With the above pattern,
* tripleo-ci-base-multinode-standard will be used as a parent in
downstream or rdo.
* Any Upstream specific multinode var can be placed in the distro
base job.
post-artifact-mult.yml playbook is used in EL8 and EL9 so
it is moved to a new role [2] tripleo-ci-post, to reuse it
at all places.
[1.] https://review.opendev.org/q/topic:cs-parenting
[2]. https://review.opendev.org/c/openstack/tripleo-ci/+/832254
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I2f3420d0be112a53c240f9e5539860e5e8673e4b
This enables the centos-9 jobs to run for stable/wallaby branch.
Mostly this removes wallaby in the negative regex we use for
the c9 branches match ^(?!stable/(train|ussuri|victoria|wallaby)).*$
The depends-on adds missing python3-dev needed by c9 wallaby
content provider.
Depends-On: https://review.opendev.org/c/openstack/tripleo-quickstart/+/830336
Change-Id: I9332b251db06ad762dadd903413cceb0666dea07
As seen with the merge of [1] some of the c9 jobs stopped running
because the branches: match between c9 and parent c8 were compliments
i.e. "^(?!stable/(train|ussuri|victoria|wallaby)).*$" vs
"^(stable/(train|ussuri|victoria|wallaby)).*$". To avoid that we
remove the direct parenting e.g. centos-9-undercloud-containers
no longer inherits from centos-8-undercloud-containers and
instead carries the required vars.
[1] https://review.opendev.org/c/openstack/tripleo-ci/+/826317
Change-Id: I99ab7f88e0e6edc25be98edf985294a3a8ef3faf
This adjusts branches: match for the centos8 jobs so we avoid
running these for master. C8 jobs will only run on train ussuri
victoria and wallaby branches. The master branch will be c9 only
moving forward.
See [1] for related patches that depends-on this across the
tripleo repos. See [2] for related dummy nodeset required for
zuul 3rd party on this review.
[1] https://review.opendev.org/q/topic:c8_teardown_master
[2] https://review.rdoproject.org/r/c/rdo-jobs/+/39045
Change-Id: If62f83de171de4e7651b58b70c31bea005710c71
This moves tripleo-ci-centos-8-undercloud-upgrade and
tripleo-ci-centos-8-scenario000-multinode-oooq-container-updates to
deprecated and removes them from the zuul layout. It adds the
c9 job to the master layout instead (no undercloud upgrade yet).
tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates
definition and check/gate layout is moved to the
upgrades-jobs-templates.yaml in line with other upgrade related jobs.
See [1] for related reviews (removal of c8 from master).
[1] https://review.opendev.org/q/topic:c8_teardown_master
Change-Id: I77ca4b99581722ccf932c515f66437211fcd594b
Makes the tripleo-ci-centos-9-containers-multinode
scenario007-multinode + scenario000-multinode-oooq-container-updates
jobs voting and moves them to the gate queue. The parent patch at [1]
deals with the content provider.
[1] Id3f4f9876602bd51d6ac6d2464b98ecb23528f8d
Change-Id: I7f1f96ec7b452c1468b49291c627a6077483f68c
This patch enable the following jobs in check for tripleo projects:
- tripleo-ci-centos-9-scenario007-multinode-oooq-container
- tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates
- tripleo-ci-centos-9-standalone-on-multinode-ipa
Change-Id: I4d7506e544ce4f01a9e0d55247cc30fc2bb6066f
Signed-off-by: Douglas Viroel <dviroel@redhat.com>
This patch adds definition of the following CS9 jobs:
- tripleo-ci-centos-9-scenario007-multinode-oooq-container
- tripleo-ci-centos-9-scenario000-multinode-oooq-container-updates
- tripleo-ci-centos-9-standalone-on-multinode-ipa
Change-Id: I4fd774b1fc3db9a881334e6388c6403b5b637faf
Signed-off-by: Douglas Viroel <dviroel@redhat.com
It enables following jobs in check as non-voting now.
* Standalone, Sc1-12
* undercloud
* Container-multinode
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I1bb7b45088d1d2b12f882cf6bbef40e38b882c5a
https://review.opendev.org/c/openstack/tripleo-ci/+/822312 adds
the job definition of undercloud and multinode job.
This patch adds it to tripleo-multinode-branchful pipeline
to run on all tripleo-ci repos.
We are keeping it seperate so that we can easily revert it.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: Iba3c7677d636e907158613c8f3e7ed60b8403f54
https://review.opendev.org/c/openstack/tripleo-ci/+/821698 adds
the job definition of sc1 to 12.
This patch adds it to tripleo-multinode-branchful pipeline
to run on all tripleo-ci repos.
We are keeping it seperate so that we can easily revert it.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I9f3dcc7a4f7766f2d882ee115c9a1fe84340795b
With the switch to ephemeral heat for the overcloud, the minion is no
longer viable. This change updates the branches to only run T->V where
the minion should work and was supported.
Related-Bug: #1938539
Change-Id: I5855de77b700124be0d0332ebe6a3f80524c521e
Patches to code in tripleo-quickstart-extras that
trigger tripleo-ci-centos-8-undercloud-upgrade
jobs are failing as
tripleo-ci-centos-8-content-provider-wallaby
was not run.
tripleo-multinode-branchful template limits the
files where the branches content providers run.
This patch reduces the irrelevant files to avoid
the freeze graph error
Currently it's equal to upgrade job set.
Change-Id: I4ea37e56dae4a3bc2e95c510e39c7af561f50088