This reverts commit e1e89f8831fd1b28b7ee373fc9504ce4eaf2c4c5.
The commit was a temporary change to allow us to unblock
the ironic CI gate as we had cross-repository fixes that
needed to land before we would be able to have a passing
and stable ironic-standalone job.
Change-Id: Ib1ed0a35955ab7c53b814048887e725234699d9a
Let's only run 2 concurrency tempest tests to see if we can
decrease the failure ratio for ironic-standlone job
Change-Id: Ifb6258df26236cf376742a051602321e9b67a52c
The CentOS 8 images we use now are much smaller than the previously
used CentOS 7 images, so hopefully we can require less RAM.
Change-Id: I39fc7c202c1f148e28c22739f3163081bfa7e0a0
We are about to drop pxe + ipxe_enabled=True combination for iPXE
testing, so let's make it explicit in the jobs.
Change-Id: I0e99e6336aa47857c06ba2f6869e66580159a9be
Story: 2007003
Task: 37779
It was changed on the primary node, but not the subnode
of the standard mutlinode job, and not updated on our
grenade job.
Changes subnode and grenade configuration to use it.
Change-Id: I8f67e3e3423e72944d22d65b788af5792ee900f9
We simply do not need to run automated cleaning on most jobs
and it has been left enabled on a number of newer jobs.
Disabling it improves gate performance by reducing the overall
wait to start tests and cycle through test nodes as sometimes
spike in testing infrastucture utilization can create increased
latency which may cause cleaning to time out.
Change-Id: I2d0d33a5b62fed536785915b2a80d7af8b6f3e0d
Adds a job to boot a node over Redfish virtual media in UEFI boot
mode.
Turns similar BIOS boot mode job non-voting to avoid CI
failure on non-essential job failure.
Change-Id: Iaabd09a7acbbd692dd72adcf6867981bcc30877e
After some testing, it seems that the real cuplrit for all the
failures we're seeing is that we're not giving enough time for the
job to complete.
This patch increase the build timeout value to 2400 secs, which
should be enough time for the job to exit successfully.
Change-Id: Ia93d7ac26a004849b97aeb98d5c5cff3df14da0f
Adds a job to boot a node over Redfish virtual media in legacy
BIOS boot mode. For sake of unification, similar PXE job has been
renamed.
Apparently, libvirt-based Redfish BMC emulation requires node
power-cycle for libvirt domain configuration changes to take
effect.
Change-Id: I2c7fc26b082db6eeae1abcd67362884a9c72c109
Otherwise Depends-On sushy-tools does not seem to work.
Depends-On: https://review.opendev.org/693561
Change-Id: Iea32b98a57713b70b535eb524b165cbeb141199f
This patch enables python3 by default in the `ironic-base` job.
All jobs that have `ironic-base` as `parent` will be running under
python3 by default.
- Switch parent/child for `ironic-tempest-functional-python2` and
`ironic-tempest-functional-python3`
- Renamed `ironic-tempest-ipa-partition-pxe_ipmitool-tinyipa-python3`
to `ironic-tempest-ipa-partition-pxe_ipmitool-tinyipa` since it was
running under python3 that it's the default now
Depends-On: https://review.opendev.org/690537
Change-Id: Ibc503baa572c2746e1e703653ddf040bad5e8363
This feature is time-consuming and prone to race conditions. This
changes switches it off by default, leaving it on in two jobs:
the one running on Nova and the standalone one.
Change-Id: I7c50cb12065da05dad4ece0918883748ee4617e0
The difference between the jobs `ironic-tempest-functional-python2`
and `ironic-tempest-functional-python3` should be only the python
version in use (for deployment and to run the functional tests).
Removing the variables `IRONIC_TEMPEST_WHOLE_DISK_IMAGE` and
`IRONIC_VM_EPHEMERAL_DISK`doesn't matter for the functional tests,
and they are set with different values in the python2 job.
Change-Id: I49ff241793f42de0f0cc9d98ae1f99940e581dcb
Also updates the devstack plugin to support pre-built DIB images
and removes the explicit mention of dhcp-all-interfaces element,
which is already a dependency of ironic-python-agent-ramdisk.
Change-Id: I564016528e80c738d6004c47f8df502a7748b311
As Dmitry suggested, we should likely just make this
a standard practice as end of cycle gate instability
makes multinode jobs blocking in nature.
We will revert this patch once things are happier,
hopefully sooner rather than later.
Change-Id: I17b853aabd1a2cddf64d73b3778d315092d5612a
For some unknown reason, new networks being created in the
fortnebula test VMs are defaulting to a MTU size of 1350 bytes.
This is based upon the physnet MTU, which does appear to be
lower on the fortnebula cloud.
Change-Id: I113973ba2a0a33c68f485d02af1ce8e12a6fbba4
Story: 2006589
Task: 36716
Moves the volume pool from / to /opt for the standalone and multinode
jobs, since on smaller nodes /opt is mounted from a larger ephemeral disk.
Change-Id: Idb4e235fd40ecd9829c3ad8a9dd1224f1c29a12e
We seem to be running out of disk space in standalone and mutlinode
jobs. Since we're creating a lot of virtual disks here, reduce each
to 4 GiB. No jobs need so much anyway. Reducing further will likely
hit issues with IPA assumptions of root devices.
Then correct setting OS_TEST_TIMEOUT in the multinode job. DevStack
variables do not affect tox runs, we need to use a new tempest
role variable instead.
Change-Id: Iceebf246b000cf77cbbf62e4edb9b06ee9dd7b71