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
In [1] we removed the related jobs for these EOL releases. Here
we deal with removing code related to these branches including
any conditionals or special cases from emit releases and the
build-containers and run-test roles. Also removes some really
old references to newton.
[1] https://review.opendev.org/c/openstack/tripleo-ci/+/838110
Change-Id: I184cd525a8696b0b634ac8d6f895ab642ac5aa33
The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.
Change-Id: Iba639e105ef6d8d9223967863ec6ac5d971be58f
Assures consistent formatting of our python codebase without having
to rely on humans to do it, or to debate during reviews.
Change-Id: I1e62cc755fa60e453dea865f436241ecae330771
emit_releases_file needed to be updated to support centos8 and
integration pipeline.
I needed to make the script distro aware, then distringuish between
distros to get the proper repo and hash in get_dlrn_hash function.
The tests have been only partially updated: I updated the success script
to cover the centos8 case, and accountfor the change in signature for
get_dlrn_hash, but the rest of the workflow is exaclty the same either
if we are in centos7 or centos8, so I did not add any additional checks.
Change-Id: I26799d5e6a3ed404b4a29be621c5871ef9be6e4c
It is needed train related upgrade jobs and fixes
the tests for the same.
It also rename the old-current-tripleo to previous-current-tripleo
in test name.
https://tree.taiga.io/project/tripleo-ci-board/task/1299
Change-Id: I9c4b6743547327457bbe1762605a48d59f4fa902
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
It's the first release that supports standalone and also LTS has not
change and it's still for queens only.
Story: https://tree.taiga.io/project/tripleo-ci-board/us/847
Change-Id: Id246cdab8a574ed57cd90813652532f47fbd0643
When looking at recent edit of emit_releases_file.py it seems that the
amount of manual unit test changes required [1] is so high that it
might deter contributors and consume too much effort.
Much of the edited unit test data seems repetitive, so my rationale
here is that we can reduce the amount of data resulting in a small
loss of coverage but considerable reduction of required labor when
making emit_releases_file amendments.
The order of side effects for get_hash function was considered for the
test result, now we use a fixture that is backed up by a tuple to a
string dictionary to configure the mock, so the order is not important
anymore.
Co-Authored-By: Quique Llorente <ellorent@redhat.com>
[1] https://review.openstack.org/#/c/606996/7/scripts/emit_releases_file/test_release_name.py
Change-Id: Ie573813a4916aeb1bb15b5aa38dc2a732586e8c2
This also add dlrn_hash_newest variable to be able to make proper repo
switching.
The $title is just adding the necessary bits into emit_release to take
standalone_upgrade into account.
The dlrn_hash_newest is a forgotten variable from the initial emit
release. It has been included for standalone upgrade where the
problem first appeared, but will likely be needed for other upgrade
jobs as well when they switch to non specific release file.
Currently we only set dlrn_hash which becomes TRIPLEO_DLRN_REPO which
becomes delorean url. We don't do anything about dlrn_hash_tag_newest
which becomes RDO_DLRN_REPO which becomes delorean-current.
This means that when we are upgrading we get the dlrn_hash_tag_newest
that was defined in the previous run, ie during deployment.
Change-Id: I0e298fc37eb7b3fd0afaa13ab021330b789b2f5e
Closes-Bug: #1795367
It also calculates the releases with the emit releses script for fs047
Depends-On: Ic578de2237f9a43ff4fcd24141802a49a06be59c
Depends-On: https://review.openstack.org/#/c/605989/
Closes-Bug: 1792892
Change-Id: Ic1aea1052a9518999f0f02539459eeef516f9654
Periodic jobs should use 'tripleo-ci-testing' hash as
a target hash, currently 'current-tripleo' was used,
this patch fixes it.
Also added unit tests for the same.
Also allow using promotion-testing-hash-$release in
upgrade job in promotion pipeline.
Closes-Bug: #1787817
Change-Id: I8893c7406fcf1bb3936f5ba2d9dca7d4a3e9e82a
Until the rocky repos are in place and working adjust
deployment to not install rocky in undercloud/overcloud.
Follow up patch required once rocky is promoted to start
installing rocky.
Change-Id: I3f714203803ddcbf72aa203c11ebbc68ad3c8def
Currently, we are only able to upgrade TO a change under test. (n-1->n)
This change adds an argument (--upgrade-from), which allows for testing
that a change does not break upgrading FROM a release. (n->n+1)
The change itself is a no-op other than changing the signature of the
compose_releases_dictionary method.
Change-Id: I141aa5e01a097968a2a3427ebcfb5b8d304c9753
This wires in the get_dlrn_hash function to the release dictionary,
so that we end up with an actual dlrn hash instead of a named hash.
Release dictionary tests updated to mock this function, including
verification of the expected calls to get_dlrn_hash.
This also adds more comprehensive logging and unittests to the
get_dlrn_hash function.
Change-Id: I41087bf0c247b933a641ea0da582b5f2b368840e
Currently, we do this in a combination of bash in this
repo and the release files themselves. However, as we begin
to support more different upgrade scenarios, this has proven
to be difficult to maintain.
Instead, we will use this python script to create a dictionary
of releases which describes which release will be used at each
point in the deploy: undercloud_install, undercloud_upgrade,
overcloud_deploy, and overcloud_upgrade.
This commit only provides an intial skeleton to work from.
Follow-up commits will provide:
1. The ability to get a DLRN hash for each of the above breakpoints
2. A CLI for the tool so it can be called from the TOCI scripts
3. The ability to parse a featureset config for upgrade variables
4. The ability to output the dictionary for consumption by TOCI scripts
Change-Id: Ibf61d7d12230f6714eb7dad91169aa043f5f8417