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
Since we have completed Upstream TripleO CI Zuul Job Reparenting.
We need to start prepration for renaming base-upstream.yaml
to base.yaml.
In order to have clean rename, remaining jobs from base.yaml
should be moved to base-upstream.yaml.
This patch does the same.
Due to Zuul Job reparenting work, base-upstream.yaml file is created
to keep the new zuul job base there.
Since Zuul job reparenting work is done, it's time to drop old
base.yaml and rename base-upstream.yaml to base.yaml.
It deletes the base.yaml and will rename the base-upstream.yaml
to base.yaml in
https://review.opendev.org/c/openstack/tripleo-ci/+/849806.
It helps to keep the changes seperate.
It updates the old job name with new parent in deprecated jobs also
to fix zuul issue.
RDO Check job review: https://review.rdoproject.org/r/c/config/+/44455
It also adds a dummy tripleo-ci-standalone-base job to avoid zuul
error.
Depends-On: https://review.rdoproject.org/r/c/config/+/44455
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: I08a5e67d31eb8c81c05b9e23d907944c566db07a
This reverts commit aa2924a3fc.
Reason for revert: all fs052 jobs are running the same set of tests, we need to fix that.
Change-Id: I7c6eab230196f469309921dbc707d00aa55470e3
Earlier we were using singlenode parent from base.yaml.
Since we have undercloud distro base jobs is already available,
we can re-use the same and remove the singlenode parent.
It also cleans up old singlenode cs8 base jobs and moves
c8s undercloud upgrade job to upgrade template.
These jobs are used as a parent in stable branches job.
https://review.rdoproject.org/r/q/topic:cs-parenting-undercloud-upgrade
cleans up the reference from rdo side.
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Change-Id: If54577079cf61d82e88aa84a414d6e3c288138b1
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
Per the topic branch [1] and discussed at [2] this removes the
centos8 buildimage* jobs from running on stable/wallaby branch.
Some jobs are removed completely as they are specific to wallaby
and centos8 (tripleo-buildimage-ironic-python-agent-centos-8-wallaby).
The tripleo-buildimage-overcloud-hardened-uefi-full-centos-8 is moved
to deprecated for now as it is still used by DIB.
As discussed during reviews this keeps overcloud-full and IPA
for C8 wallaby for now - they may be removed by a subsequent patch.
[1] https://review.opendev.org/q/topic:c8_wallaby_teardown
[2] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027403.html
Change-Id: I04526b2c7f90ab9399fb92c86a0da216024acd30
This removes the standalone/scenarios from running on stable
wallaby.
This includes a tidy up of the layout to avoid a lot of
repetition using yaml anchors/overrides. This is related to
the change as we had to use branches: overrides on the centos9
jobs in the layout (as well as the existing c8 ones) which
became very messy/long.
Also include reparenting for the scenario standalones as
they were inheriting from the 8 equivalent directly with
inverse branches: matches. See [1] for more context and [2]
for topic branch/test patches.
Removes obsolete c8 jobs like
tripleo-ci-centos-8-scenario010-standalone-wallaby
tripleo-ci-centos-8-scenario010-ovn-provider-standalone-wallaby
tripleo-ci-centos-8-scenario010-ovn-provider-standalone
Moves tripleo-ci-centos-8-scenario010-standalone deprecated for now
[1] http://lists.openstack.org/pipermail/openstack-discuss/2022-February/027403.html
[2] https://review.opendev.org/q/topic:c8_wallaby_teardown
Change-Id: I67bec4b9d25cf1a3d1c55f254e9c321ed979b172
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
This deprecates the non-content provider tripleo-undercloud-jobs
template as part of a wider tripleo-ci optimisation
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
Change-Id: Id4c6f1d781cb202c996850074c5e4fc3e29ed83a
Moves the tripleo-standalone-scenarios-full and -multinode-ipa
to deprecated-jobs.yaml as part of our CI optimisation [1]
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
Change-Id: I2f7d3dd9730dc30284bb52e3eca73375c7d550d2
As part of CI optimisation at [1] this deprecates the following
multinode templates:
* tripleo-multinode-baremetal-minimal
* tripleo-multinode-baremetal-full
* tripleo-multinode-container-full
* tripleo-multinode-container-minimal
* tripleo-multinode-tripleoci
These are still used in some places such as [2][3] so we need
to remove those before we can delete the templates alltogether.
This also removes the standalone and undercloud jobs from the
multinode template. It is confusing to have them there and
increases the maintenance burden for the tripleo-ci team.
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
[2] https://review.opendev.org/c/openstack/os-apply-config/+/777097
[3] https://review.opendev.org/c/openstack/os-refresh-config/+/777098
Change-Id: Ie6473759383bd4b903cbe56fba9fee75a24154c4
As tracked at [1] and part of wider CI optimization, this moves the
non voting tripleo-ci-centos-7-containers-multinode-train -queens
jobs to deprecated and removes them from the zuul check and
experimental layout.
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
Change-Id: I1477b4aed27cd85df12809578768720068163a5c
These jobs are non voting and deprecating these is part of a wider
effort to reduce our CI footprint see [1]. Deprecating instead of
removing so we don't block on places still using them, like [2].
Once they are removed from all layouts we can delete them from
deprecated-jobs.yaml
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
[2] https://review.opendev.org/c/openstack/aodh/+/776116
Change-Id: I93dadae4999679b5f54acdc1c459ce5806b1386e
This moves the standalone, undercloud and scen0 overcloud master
upgrade jobs to deprecated and removes them from the various
layouts.
Moving to deprecated vs removing them allows us to merge this patch
without blocking on the removal of these jobs from any other repos
that are still running them such as [1].
This move was discussed on the openstack-discuss list at [2].
[1] https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/774916
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020365.html
Co-Authored-By: Marios Andreou <marios@redhat.com>
Change-Id: I16f3a2df156a125c2ea18c7d43b9b193d31b2c2d
As we are going to migrate train jobs from centos 7 to centos 8.
Here this change is going to deprecate dedicated centos 7 train jobs
and remove it from job template.
Job list:
1. tripleo-ci-centos-7-scenario007-standalone
2. tripleo-ci-centos-7-containers-undercloud-minion
tripleo-ci-centos-7-standalone-os-tempest job will run only stable/stein.
[1]: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016157.html
Change-Id: Ia4ea1bf8830a5b7a9c76b2ba1daf9ec89bb96177
Signed-off-by: Bhagyashri Shewale <bshewale@redhat.com>
Job tripleo-ci-centos-7-scenario009-multinode-oooq-container was
failing since long time and it is not required in upstream.
Related-Bug: #1874019
Change-Id: I7692192ec85a7f4a0e6b8af42552aa17db882f05
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Non-containerized jobs were running for stable/newton and
stable/ocata branches and are no longer supported.
- Move deprecated jobs into a separate zuul config file
- Reparent deprecated jobs to tripleo-ci-deprecated
- Add a playbook with deprecated warning
- Disable jobs with 'branches: none/deprecated' filter
- Remove/disable non-containerized scenario jobs from layout
- Add noop to templates with non-contrainerized jobs only
* tripleo-multinode-baremetal-minimal template
* tripleo-multinode-baremetal-full template
- Rename (create a copy for) scen006 and scen009 with a
'-container' suffix as these are containerized
As tripleo-ci repo is not branched, all the projects that have
these jobs in their zuul config (including all branches) will be
affected. Therefore, a cleanup is required to deprecate jobs before
removing them from zuul config. A follow-up change will *delete*
the definition of deprecated jobs from zuul config,
Story: https://tree.taiga.io/project/tripleo-ci-board/issue/372
Change-Id: I23df3518820d39f32d1daded33776d757c144217
Zuul