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
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
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
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
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
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:
https://review.opendev.org/c/openstack/ironic/+/783722
Change-Id: Ifffeac9c1c4d394526d655eaa14c9fe7bd3a1e5e
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'll keep using bionic as nodeset for certain jobs because of limitations
in DIB when building centos images.
DIB uses yum-tools to prepare the chroot environment, but the package is
not present in ubuntu focal because of lack of Python 2.x support.
Change-Id: I8635b7dfa6910c1721b89739d4d51fa7df488432
The IPA images we presently build/use for centos are
now smaller than their peak size a few months ago.
As such, we should be able to reduce that memory footprint
and still execcute all of the necessary tests without any
issues.
Also increases the amount of swap to 8GB as the infra
default is now 1GB.
Change-Id: I5705f1f2504803a049ed88a0d8b1d6d0bbccf9e4
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.
Change-Id: Id5efe89a12a00c27e6299380a51cdb840285d691
Also add some info on external projects that use current jobs.
Depends-On: https://review.opendev.org/749723
Change-Id: Ifeffebf2264993e1773a1e9867380523ec49a93f
The ironic-standalone-ipa-src job uses tinyipa, which should be
ready to be moved to use Ubuntu Focal.
This will allow us to move to build tinyipa with tinycore 11 in
ipa-builder.
Depends-On: https://review.opendev.org/749357
Change-Id: I3548ca1ecb16cdefd6e51e379d5d7458e13f9ec4
Riccardo Pittau
OpenStack Release Bot