openstack/ironic-python-agent - ironic-python-agent - OpenDev: Free Software Needs Free Tools

The use of job ipa-tempest-bios-ipmi-direct-tinyipa-src was
already removed in https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/950235
Change-Id: Ib67d8d502fbc0f77282ea0e01a68334ec464acb3
Signed-off-by: Julia Kreger <juliaashleykreger@gmail.com>

Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/950235
Change-Id: I44fd4cd6e9cc52f884d14a5c8d0478d02d5b57ee

The non-redfish standalone job is pending removal from Ironic.
Change-Id: I2b6d542ce7af3eeeff23f06e43e82de5d7b09701

Change-Id: I938eaaf29e3bc803155baa11b450d4d92e349d58

Change-Id: Ia299f19f6348c35f6052efc78c7cb6b3093703ba

It is not a valid check to import the hwm without it being loaded into
IPA first, as objects such as the configuration object won't be loaded
yet.
Change-Id: Icf20e71e8061bb886885c1b2e29bd13ccac37ade

Change-Id: I64909aa932635b729cc85717dc241ae31798b558

Python regexes are deprecated in Zuul, so this commit updates the
configuration to use RE2-compatible syntax.
Change-Id: I19b81e4999f9c130e18872593df9dccb416e9e6a

We've proven the concept, it's a good check, let's enforce it!
Change-Id: Ie3a5410066ef628949146f825303934110b19134
Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent/+/920153 

Updating tests after change [1] and [2] in ironic-lib.
[1] ae53e8e4b3
[2] 7644196e7d
Change-Id: I880b4f82beb117d8812e60c13040e19476cec32b

Adding CI for previous codespell tox change
Related Bug: https://bugs.launchpad.net/ironic-python-agent/+bug/2047654
Change-Id: I02f7973c0e6799f7d7b44978009dfebbce3877a4

Instead of the old dusty cs8 one.
Depends-On: I56a0473ecbff8ab8fc143954d3c493037765cdf1
Change-Id: I7bf9cbff9d10299c1a6b9b19fddd8124c1b185ba

Bandit 1.7.5 released with a timeout check for all requests and
urllib calls.
Fixed those.
In the process, then exposed a bandit b310 issue, which was already
covered by the code, but explicitly marked it as such.
Also, enables bandit checks to be voting for CI..
Change-Id: If0e87790191f5f3648366d571e1d85dd7393a548

- Disable auto discovery in setuptools
This is to avoid issues with latest setuptools after version 61.0
For more info see [1]
- add bash script to allowlist in tox.ini
- use default size for vm memory
[1] https://github.com/pypa/setuptools/issues/3197
Change-Id: Iae24917add1aae6b1ed46dba0d2c270b39c5698c

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for antelope. Also,
updating the template name to generic one.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I91232b32f26842802fc42c1d9e28a6ea791ecb7b

This is a non-voting job to validate py3 unittests on ARM64
Change-Id: I608d2e4e9e378b1f6e33a7e1a2cdc1c0bab7ec5c

Change-Id: I2b4c543537dac8904028fdcdb590c1c214238e10

The ipa-tox-examples job is voting but it's missing from gate
Change-Id: Ie47066084172d8e06eb1f6f097b0354b3b800612

Please see:
https://zuul-ci.org/docs/zuul/latest/releasenotes.html#relnotes-4-1-0-deprecation-notes
Change-Id: I341b8a2220a49c5a7c3f78fed3a1baa0f0638cde

With netboot removal, this will be the only job that tests local legacy
boot with partition images.
Depends-On: https://review.opendev.org/c/openstack/metalsmith/+/841911
Change-Id: Id3f165286cfc47dcf45c042115a63804a0c671e8

IPA can no longer be installed on them, other projects will follow.
Change-Id: I945520d912564be610cee3990bad827549747904
Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/841562 

As discussed in TC PTG[1] and TC resolution[2], we are
dropping the lower-constraints.txt file and its testing.
We will keep lower bounds in the requirements.txt file but
with a note that these are not tested lower bounds and we
try our best to keep them updated.
[1] https://etherpad.opendev.org/p/tc-zed-ptg#L326
[2] https://governance.openstack.org/tc/resolutions/20220414-drop-lower-constraints.html#proposal
Change-Id: I16ea0a61c018d03d6c23e0b0736295a36b6dd367

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for zed.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: I25719dcd3035816d934b806ae129051df322bf9c

We recently enabled voting CS9 jobs in ipa-builder, let's also add the
same check job here.
Change-Id: Iaf2e56e0a1f6ca35272bcaedf3cb73273080b7ef

Its configuration must match one in Ironic, and netboot does not work
with whole disk images under UEFI.
Fix the boot mode of the BIOS job: it was running in UEFI.
Change-Id: Ia207e80bbfc30f8d2891e11bbeda7b2ab0d617c0

Currently it requires tracing the jobs up to the ironic's devstack
plugin. Be explicit.
Change-Id: I19d0e680b0025bda22709c5a4fff9eacb5b4b1d0

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.
Change-Id: I2446afeaca866ffc3131b5e9f266526f35fc5ed7

TC has decided to keep support for Python 3.6 during the Yoga cycle.
For more info see [1]
[1] http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026164.html
Change-Id: Icfe518fafa2b012e034a2e8ff18c242843df0086

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.
Change-Id: I97ad7c4acdb278e2849a598c5a02a71fc67cc81a

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.
Change-Id: I4cbc359ceabfc193ce18fed14a1952359460e7d9

Change-Id: I523382b5b06b479ba34dce5a1dc7262076122514

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for yoga.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ia08ee369e2925b2c313dcfaa8975fe023ec1c07a

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.
Change-Id: Ic9cef3e56266c6e9de0936b5f113e8b38d705a9b

Remove the jobs that are now redundant.
Depends-On: https://review.opendev.org/c/openstack/diskimage-builder/+/788972
Depends-On: https://review.opendev.org/c/openstack/ironic-python-agent-builder/+/788971
Change-Id: Ic0b7bc509652c23cec85e685d66de368fdc4761d

This is an automatically generated patch to ensure unit testing
is in place for all the of the tested runtimes for xena.
See also the PTI in governance [1].
[1]: https://governance.openstack.org/tc/reference/project-testing-interface.html
Change-Id: Ib3d406de284d5b2211eebb03e71ca92ce93bc01f

Depends-On: https://review.opendev.org/c/openstack/ironic/+/783722
Change-Id: I4905c17d2e78ed02e9005ffbd93b036674e6ff51

Follow-up to 8dd6589e66: 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:
https://review.opendev.org/c/openstack/ironic/+/783722
Change-Id: Ifffeac9c1c4d394526d655eaa14c9fe7bd3a1e5e

Tinycore 12 requires some more RAM than its predecessor.
Change-Id: I642ccdcef43361b5648a9652d041ebb6dfe6a0e9

As discussed during the upstream ironic community meeting on
Monday Dec 14 2020, the lower-constraints job is being removed.
Change-Id: Ide0f6c38a59ae6486fa33cfb19b383d022e57d5a

The ironic-ipa-base is based on ironic-base that is already running
on ubuntu focal, non need to specify nodeset for those jobs that
are based on it.
Change-Id: I7ffb920442d5e33ef5014152b72b9ac32e367047

Also disabling dstat in all focal based jobs because of
https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619
Plus including increase of alloc memory to increase job
success rate, original change from [1]
And re-enabling ipa-tempest-bios-ipmi-direct-src and
ipa-tempest-bios-ipmi-iscsi-src
[1] https://review.opendev.org/759765
Co-authored-by: Julia Kreger <juliaashleykreger@gmail.com>
Change-Id: Ia154745b71c17063eeaaabeb56950ab1cc9ce927

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.
 https://review.opendev.org/#/c/757141/
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.
 https://review.opendev.org/759906
Also disabling ipa-tempest-bios-ipmi-direct-src and
ipa-tempest-bios-ipmi-iscsi-src for the time being, will revert
in https://review.opendev.org/757812
Change-Id: I08c8c258587dd3786dfa92e7879a80c80971d7df

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
filesystems.
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
centos8.
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[0] mentions
this issue, Another bug [1] 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. :\
[0]: https://bugzilla.redhat.com/show_bug.cgi?id=1744693
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1709682
Depends-On: https://review.opendev.org/#/c/748315
Change-Id: I14bf299afef3a1ddb2006fe5f182d7f0d249e734

We can use focal here but we need to disable dstat because of
https://bugs.launchpad.net/ubuntu/+source/dstat/+bug/1866619
Change-Id: I2c013e871fc56aa0077656dfc76de9aad6bed83f