The standalone job seems to be the most problematic CI job
in ironic's CI jobs at this point in time. While we've moved
to unsafe disk caching for the test VMs, there are times when
the devstack instance is still being crushed with IO wait for
multiple seconds.
This could be from processes in the VM or just a noisy neighbor
but first lets try to lower the concurrency to hopefully make
the job more reliable.
Change-Id: I4dfeb3407cfe4064a5d93a4ed3657677fa5237ef
It's just a library we consume, there is no reason to use its
git head. Currently 1.4.0 is breaking us.
Story: #2006301
Task: #36014
Change-Id: Ib1b1e32bc60d7ec271098dcd17086f79518c09df
The has stopped working out of a sudden. We should move to tempest_plugins
zuul variable later on, but it is only available since Stein.
Change-Id: I2cc64580b089566e664d54ea2087878b9cce6666
Adds bandit configuration template and exclude some of
tests that we don't want to fix for the moment.
Keeping job unvoted so that we can keep an eye on possible
issues while not breaking gate.
Change-Id: Ic577cad3b61421c04023ea887236992acb19f77c
Story: 2005791
Task: 33518
Fixes the grub2 based devstack logic and adds a grub2 CI job
such that the ironic team can safely clean-up some of the PXE
code without fear of breaking the grub2 scenario.
Story: 2003936
Task: 27724
Change-Id: Ieb395bf35e2689741a243c11b56d08a237b200bc
This goal is to implement the process set out in the 2018-10-24 Python
Update Process TC resolution[1], for the Train cycle to ensure unit
testing is in place for all of the Tested Runtimes for Train[2].
In practice, this generally means adding unit tests for Python 3.7 and dropping
unit tests for Python 3.5. Using the Zuul template for Train will ensure that
all projects that support Python3 will be tested against the agreed runtime
versions, and make it easier to update them in future.
[1]https://governance.openstack.org/tc/resolutions/20181024-python-update-process.html
[2]https://governance.openstack.org/tc/reference/runtimes/train.html
Change-Id: I06e6c071b8bd369c8a66bade2490f65070fd0665
Depends-On: https://review.opendev.org/#/c/641878/
The multinode jobs are failing because the br-infra bridge
is not being setup. It is not being setup because somewhere
in the infra, the multi-node-bridge role is never established
as a requirement. Realistically, only ironic does this, but
we need to ensure it is present.
Change-Id: Ia1dcc68d7e75a931e01829ce23da36c978a70765
The PUBLIC_BRIDGE parameter, for most multinode zuul jobs
defaults to br-infra in cases where native zuul configuration
is used.
However, this is not true for legacy jobs still using devstack-gate.
When jobs are invoked with devstack-gate, the bridge must be set
to match the devstack-gate scripting as zuul *does not* setup the
vxlan bridge for us. Devstack-gate does so.
Change-Id: I37bff3c4d930ada483690d0dea17cb9a64d51fd2
Seems the bridg name has changed, and until we're
able to get it sorted, lets mark it non-voting such
that we're able to land other code... and actually
land any fixes since the changes ideally need to
merge to stable/stein first given grenade's
operating model.
Change-Id: Ibeb89003416b398c199d605744eadf408927de45
In ubuntu bionic, the UEFI provided in the ovmf package version
0~20180205.c0d9813c-2, EFI v2.70 by EDK II, seems broken and
causes kernel panic.
To be able to boot using uefi, we download and install the old
working version 2.60 from the multiverse repository.
Story: 2004604
Task: 28500
Change-Id: I1a5b4a6544621316f71203282f7418d2001ad357
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ie1be8a026e88eba235bce29fe0504e35e03afe8e
Provides a facility to minimize the power state changes of
a baremetal node to save critical time during deployment
operations.
Story: #2004965
Task: #29408
Depends-On: https://review.openstack.org/636778
Change-Id: I7ebbaddb33b38c87246c10165339ac4bac0ac6fc
Adds unit-with-driver-libs-python3 tox environment, and corresponding
ironic-with-driver-libs-python3 Zuul job.
The lack of this job was highlighted by
https://review.openstack.org/#/c/641972 which marks UcsSdk as supported
in python 2 only.
Change-Id: Ibc0f9a8fddd8f6b358efed1c4c93b95d4e01bc13
This patch adds the option to configure the python interpreter
that is used when deploying machines using the ansible deploy
interface.
Also set the default interpreter for tinyipa image with
ansible deploy interface to /usr/bin/python3 on devstack
and marks ironic-standalone job as voting again.
Change-Id: I8eb58fb00980c9e8946e3b3ef77611a9f5212668
Story: #2005159
Task: #29877
The ironic-standalone job is failing because the most recent IPA
image has only python3 and ansible uses python 2 as default
interpreter, resulting in a /usr/bin/python not found error.
Marking ironic-standalone non voting and removing it from the
gate until we can run ansible with python3 on remote machines.
Change-Id: I56768d7c8a577f267172de02d77e2cc2ead785ad
Using AMQP-based RPC can be an overkill in case of ironic, especially
when used standalone. This change allows using a built-in JSON RPC
implementation instead.
This implementation does not currently support the object indirection
API, which does not seem to be used anywhere anyway.
The standalone and API test jobs are changed to use JSON RPC.
Story: #2004874
Task: #29141
Change-Id: I7cc95935d6bdae43fab5dfbd544c8e6d65fcc38d
This is a follow-up from I96a96a9d6f23f02f9f49c962f183e8c5ca78e048
Removing the duplicated jobs after we have the patches for other
repositories merged.
Also we have refactor the jobs so we can use ironic-base in other
repositories jobs to avoid unnecessary code duplication
Depends-On: https://review.openstack.org/#/c/629494/
Change-Id: Icd4a486f176c8d7dbd78426c39097c169f27c0ae
According to [1] the dsvm should be removed from zuulv3 jobs
[1] https://docs.openstack.org/infra/manual/drivers.html#naming-with-zuul-v3
Duplicate jobs to avoid break the gate in other projects like:
- ironic-tempest-plugin, ironic-inspector, nova, neutron, devstack
Change-Id: I96a96a9d6f23f02f9f49c962f183e8c5ca78e048
This supports ext4 partitions with metadata_csum(as created
by ubuntu bionic by default).
Also Using it with the e1000 virt driver cirros sees the nics.
This allows us to remove 2 of the special cases we had inserted
when the CI jobs were switched to bionic.
Change-Id: I68165110dd57ed314cbc29430f84ff5092065d38
Story: #2004604
Task: #28570
Task: #28499
The version if qemu-ipxe on bionic doesn't attempt
to network boot when using virtio-net.
Change-Id: I335a2a0a8a82bb43a06202f96e629aa72d10cfac
Story: #2004604
Task: #28498
Switch back from bionic to xenial while we sort
out the various priblems in CI
Change-Id: Ie7341654077273f0dd3a682449c3c61fcffee5c8
Story: #2004604
Task: #28497
When validations occur, we raise an exception internally
which can lead to confusing and misleading log messages
when whole disk images are utilized with the standing
default of network booting on neutron.
We've long discussed changing it, so why not start.
Change-Id: I68bb1b9bf8c14ba686eb1c9d2755badf84481f91
On slower nodes, sometimes Ironic can take up to ten
minutes for the deployment to complete. The downside is
that the tempest build timout is set to ten minutes.
In order to reduce the number of erronious failures
and rechecks, extending the timer to 12 minutes which
should provide enough time for the deployment to complete
to tempest's satistfaction.
Change-Id: Ie883d641d0951cb148e8cfb812b9607fa77ddb4b
We don't need to test cleaning with some of the integration tests
where ultimately we are only testing a slightly different scenario
with an unrelated code path.
Change-Id: Ic7825a12763c07956e812fe509c455989868590d
We already broke openstacksdk CI with our changes once, and now we
broke it again with an ironic-inspector change. Let us add a job
to add coverage for bifrost and openstacksdk code paths.
Start non-voting since our CI is already a bit unstable.
Change-Id: I1277b52067efbfcc4119b60678f356397a82166c
Depends-On: https://review.openstack.org/618726
This now appears to need more then the bios jobs. A recent
update to one of the components of the tiny IPA image appears
to have increased the requirements.
Change-Id: Ia38ab45d0b1d7f7c57a2be71cf290de02ab86e6f
Story: 2004355
Task: 27954
As Nova's CI jobs can call the ironic-tempest-dsvm-bfv job,
it seemed to only make sense to keep that job name and have it
leverage the ipxe boot interface instead.
The newer named job, ironic-tempest-dsvm-ipxe-bfv only exists
in the ironic repository according to codesearch.openstack.org.
This removes one un-necessary check in the ironic check gate.
Change-Id: I55bd2e7e5fa5d10ca6ed3093ebabf7dc3be07fb9