Add file to the reno documentation build to show release notes for
stable/2025.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2025.1.
Sem-Ver: feature
Change-Id: Ifba45404d3c12427fc80e3d7cdab11b357d358ac
Due to change in ansible-collections-openstack baremetal_node_info
module introduced by commit 902b2f8, node UUID is no longer stored in
`uuid` field and `id` is used instead. Due to this deploy-dynamic
playbook may no longer work in certain scenarios. This change updates
the field to match the ansible module.
Change-Id: I3e830e1c6caa85437c4aa6fbc95e5d384ee9562d
Bifrost CLI takes `--configdrive` parameter while the documentation
states `--config-drive`. This commit fixes the typo.
Change-Id: Id1417f65e4e32183c21df62f65e73e4fc04afca7
The bifrost-upgrade jobs should upgrade from 2024.2 (Dalmatian).
Since the upcoming 2025.1 release (Epoxy) is a SLURP release, the
bifrost-slurp-upgrade job should upgrade from 2024.1 (Caracal).
Change-Id: I8efff0f9fed47f4d6102a663bee2597b41466299
Instead of assuming the python version based on the distro, we
check the python version. (Check borrowed from bifrost-cli)
This patch defaults to the newer ansible version, and if python
is old, we override it with the old ansible package.
This lets us install on the RHELatives like Alma and Rocky, which
the current check is preventing.
Change-Id: I47413eab8c5132ab3201b4c7197ec15c17d18e12
Python 3.8 was removed from the tested runtimes for 2024.2[1] and has
not been tested since then.
Also add Python 3.12 which is part of the tested runtimes for 2025.1.
Now unit tests job with Python 3.12 is voting.
[1] https://governance.openstack.org/tc/reference/runtimes/2024.2.html
Change-Id: Id6ebe6cb306e8f73d93701333da9b2eff76c849d
The old pinned image no longer exists. Switching to the latest image to
match Rocky and Ubuntu. This also avoids issues when old images are
removed.
Change-Id: Ibcecffe6d750b9c8a2e420276701d85c6caf130b
For Rocky Linux, the checksum file format differs from Ubuntu. The
current awk expression failed to extract the correct checksum and would
instead output SHA256. This caused checksum validation to fail. A
similar issue exists for CirrOS which uses the MD5 algorithm.
Changes the logic to first extract the line with the corresponding
image name and then searches for a string that looks like a checksum
within that line.
Closes-Bug: #2081031
Change-Id: Id426db0ad418898a2ebe9f2b5001945520dc6b1d
Add file to the reno documentation build to show release notes for
stable/2024.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.2.
Sem-Ver: feature
Change-Id: I588c7db8c9e8900dd21c9b6420213fca2ef3e69a
This change adds automatic configuration of enabled_firmware_interfaces based
on the enabled_drivers parameter passed during installation.
Change-Id: Iab8b4324a53e4764edd1994d1fb9f7fb24e2e939
We keep testing Ansible 8.x in CentOS Stream 9, while we start
testing Ansible 9.x in ubuntu and debian.
This is mainly because in CentOS Stream 9 we have Python 3.9
but Ansible 9 requires at least Python 3.10.
Change-Id: If2fcae6eb3d00a7488fd237ae155c337c0747e20
Move remaining os-default files to vars directory, where the
include_vars expects them to be.
Use a first_found lookup instead of a with_first_found loop so that
the 'paths' parameter can be used.
This ensures that only vars from the role are included, and not vars
from a parent calling role. This can happen when a parent role has
a higher priority vars file available for inclusion than the role
it calls.
Change-Id: I49c041b2217c51048fa182106009d334b6b38f6f
There's very little difference in the package lists. I'm just
guessing there, but I believe g++ and xml2/xslt devel packages are
for working with libvirt, and the python3-selinux either comes
pre-installed or is installed at some earlier point by other
playbooks.
Change-Id: I5865c65cae695491524a8828c8abb48393a197a0
