We forgot to revert it. This job covers software RAID and manual
cleaning, so it's very important to avoid regressions, even if it costs
us some rechecks from time to time.
As discussed during the ironic meeting on 29/11/2021, the community has
decided to continue testing the code against Python 3.6 to keep
compatibility with distributions that have native support for it, such
as CentOS Stream 8, Ubuntu Bionic, Debian 10, and openSuse Leap, at
least until it's possible and reasonable considering the support granted
from other dependencies and libraries, and not beyond the Yoga cycle.
This function returns the complete block device record, not just number.
Fixes regression in 89bc73aa01.
Also fix the incorrect job in the gate queue, which prevented us from
catching this issue on merging.
The lower-constraints test was removed because of an issue where pip
could not correctly determine the required packages versions to install,
ending in an almost infinite loop that would end up in timeout, failure,
and general mayhem.
Recently the issue has been fixed and, if properly configured, the
lower-constraints test can provide good indication of which minimum
versions are required to support the current code.
This patch adds the test back to the current development branch, and it
runs only on master.
The lower-constraints file will stay in the future stable branches.
Follow-up to 8dd6589e66d03e45e1d510601da9531a30842cff: PATH is not a
valid lsblk tag, we need to use KNAME with -p flag.
Also add a vmedia job to avoid breakages in the future. It's added
non-voting because we have a deadlock with this change:
The standalone job at present has a high chance of failure
due to two separate things occuring:
1) The deployed nodes from raid tests can be left in a dirty state
as the raid configuration remains and is chosen as the root
device for the next deployment. IF this is chosen by any job,
such as rescue or a deployment test that attempts to login,
then the job fails with unable to ssh. The fix for this is
in the ironic-tempest-plugin but we need to get other fixes
into stablilize the gate first.
2) Long running scenarios run in cleaning such as deployment with
RAID in the standalone suite can encounter conditions where
the conductor tries to send the next command along before the
present configuration command has completed. An example is
downloading the image is still running, while a heartbeat
has occured in the background and the conductor then seeks
to perform a second action. This then causes the entire
deployment to fail, even though it was transitory.
This should be a relatively easy fix.
Also disabling ipa-tempest-bios-ipmi-direct-src and
ipa-tempest-bios-ipmi-iscsi-src for the time being, will revert
By default, grub2-mkconfig scans everything to look for other
environments and then load those into the grub configuration.
It makes sense, but on newer versions of grub2 in distribution
images, os-prober is taking an exceptionally long time in some
cases where more than one storage device exists with other
As a result, of the os-prober execution by grub2-mkconfig, the
bootloader installation can completely time out and fail the
deployment. This is presently experienced with metalsmith on
There are numerous sporatic reports of issues like this issue
where grub2-mkconfig hangs for some period of time, and this is
observable on Centos8.2 in our CI. While one report mentions
this issue, Another bug  has the dialog that actually helps us
frame the context as to what we likely should do.
Also, fixes the unit testing so we actually test if we're running
with grub2. :\
Apparently, functional-py36 just runs unit tests.
Fix the test that has regressed in the meantime and make it voting
so that we don't regress again.
They're not easily discoverable there, let's keep them in tree.
The examples have been restructured to have two different projects
ready to be copied and adjusted. PEP8 failures have been fixed.
Co-Authored-By: Jay Faulkner <email@example.com>
- Increase the number of VM's since we are running two tests.
- Do no run ipa-tempest-wholedisk-* (the partition jobs are covering
this since tempest runs wholedisk and partition tests)
- Remove `partition` from the job names
This patch converts the main jobs to dib images.
The discrepancy in the names is due to the fact that some other
projects, like diskimage-builder and ironic-python-agent-builder,
use those jobs, so we leave them for the time being.
The same thing happen for the tinyipa jobs, we create some ad-hoc
jobs until we convert the jobs in the other projects.
This job is the only job that is currently testing partition images
with local boot. Due to its usage of a custom centos instance image,
there is some potential instability, but recent runs  have been
While on this code, change the lower-constraints jobs to a template.
- removed `USE_PYTHON3` from ironic-ipa-base since ironic-base
already has this configuration
- Enabled python3 for ipa-tempest-wholedisk-bios-ipmi-direct-tinyipa-src
- Renamed ipa-tempest-dsvm-partition-ipmi-iscsi-tinyipa-python3 to