Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: I844d71c552a6faf98f6ded9dd060161ecd79577b
Third in a series of commits to add Codespell to Ironic Repos. This commit adds the Tox Target to CI
A future commit could potentially add a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: Ica261e5e528bde8ec4f1627f3560e8c2022e3370
Second in a series of commits to add Codespell to Ironic Repos. This one adds the command that was used to fix the spelling errors.
Future Commits will add CI support and potentially a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: Ie6d9f79138c39a530daeb471b2cf4a9bf19b5a98
This is the first in a series of commits to add support for codespell. This is continuning the process completed in ironic-python-agent.
Future Commits will add a Tox Target, CI support and potentially a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: I6ce80cc993cdd4c8d38266f3ff3f8f134f0fc5a9
Bullseye requires installing lshw from backports because the default one
has broken JSON output:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002025
Bookworm requires installing firmware from a different repository.
Change-Id: I1bfecfcaff1547f99fcb48cc54b8f7ff77f0b0d9
The USE_PYTHON3 option has been defaulted to true for
some time, and is no longer used. It was initially added
to enable adoption of python3, we have long moved past
needing to choose between python2 and python3, and
default on python3.
Also, since python2 is no longer supported, this makes
the code cleaner to read.
Change-Id: Ia9e62634c954446b0b47067fcdcd28cac49fbf4b
Moving from networking to systemd-networkd for debian
Original networking is not capable to natively manage down/up on
interfaces that is necessary for rescue
Change-Id: Ia6e2f217bd3222641cc1c97931e776e7fb717755
When creating the rescue user, check if we are on Debian or RH based
in order to use the right sudo group
Change-Id: I894f47a1eb0ecbccbecc0900980de7ad9da72425
It appears openstack/project-config is still set to focal for image
artifact builds/uploads. After discussing with opendev infra team,
we think we might be crashing the host vm on the focal kernel
leaving us with minimal information to troubleshoot.
The cleanest path forward is to match what we run the check job on
which is Ubuntu Jammy, as a data point before we change the overall
project-config.
Change-Id: I9d6581132569b4a921e8cbc0a1b10c73a6aeba0d
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I3f44e26bf28da82d88a03995856c0837ceae0052
We use IPA ramdisk image as a minimal operating system to execute firmware updates for disks/NICs, i.e. things that cannot be updated through BMC. This requires the ability to run Ansible.
Closes-Bug: rhbz#2234514
Closes-Bug: 2032981
Change-Id: Ic6fbc5f48ddd385a9bbbbabebe0a2c5980142c6f
- update kernel module versions
- mount efivar partition manually as it's not done automatically
anymore in recent kernels
- link /bin/sh to bash as it's not done automatically anymore
Change-Id: Ic17ffa07e8429a88326f70addda7eebd2a6dbef6
fio packaging previously contained everything in one RPM,
but at some point for EL9 builds, this was split into multiple
RPMs where each engine used was put into it's own RPM.
In order for integrated disk benchmarking to work with
introspection, we use python-hardware. Python-hardware uses
fio, with libaio as a default option.
So now, we will attempt to install the other package which
should make users of the feature happier as their ramdisk
images will come with the contents required to do a benchmark
upfront.
Change-Id: I2028ac1cf350d86903a33e4bd91c209887de1e5c
Followup on I2dd1c60e3bfd9c823a7382b1390b1d40c52a5c97
Change-Id: I5e2d454fb84b76810f3c5ed26a0caeef8ea06675
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Upgraded to latest hacking. Also had to bump the upper limit for
pycodestyle to be in line with other repos in order for pip to be happy
installing new hacking.
Change-Id: I4fd9e1e135b6759738f7faecfe8a8a046274d566
Remove focal support
This is long due
DO not use tmpfs to build the jammy image, use the disk space instead.
This is to avoid increasing the tmpfs mounted partition, we have 80gb
disk space available.
Change-Id: I6d6ebbb217886ed0e65137b8c8f0825d97abec81
Currently the dib images are built on tmpfs mounted partition.
As the images become bigger and bigger we may want to use disk
space instead of increasing the tmpfs, considering that a
standard VM in CI has around 80gb disk space while only
8gb of RAM.
Change-Id: Ifbb1f38700e6b57e1da7be80c27c532aa9949493
Currently the latest RDO repo is installed on centos9
for the python-hardware package. This would not be appropriate in the
following cases:
* When repos are copied in from the host via DIB_YUM_REPO_CONF
* When another element is responsible for setting up repos
This change adds environment variable DIB_IPA_HARDWARE_RDO, which will
only be set to `1` on centos9, when DIB_YUM_REPO_CONF isn't set, and
when the user hasn't explicitly set DIB_IPA_HARDWARE_RDO.
This retains the current default behaviour of just working, while
giving flexibility for repos to be set up another way.
Change-Id: I1cc0b9833baf642866e9762c6bae44360bffe20d
OpenStack Release Bot
Zuul