If enabled, rabbit is required for all ironic services, so it makes
no sense to only configure it when API is enabled. This seems to
break multinode grenade, since `is_service_enabled ir-api` returns
false on the subnode. Try to configure the RPC backend in all cases
when IRONIC_RPC_TRANSPORT is "oslo" (not JSON RPC).
Also move the automated_clean option to the conductor where it belongs.
Change-Id: I6e046c6b6e1e4c0ca7bfd5fb9ce5892c0298fb78
Following recent changes to global requirements [1], we need
to update sphinx requirements locally.
[1] If558f184c959e4b63b56dec3ca1571d1034cfe5c
Change-Id: Ia0dd6883b4c15b8a0646ee765689343c116b2bcd
Fixes GRUB configuration file generation procedure when building
bootable ISO images that include user EFI boot loader image.
Prior to this fix, no bootable ISO image could be generated
unless EFI boot loader is extracted from deploy ISO image.
Change-Id: I1a761737958662cef45885e54cf7532babae1ee1
Story: 2005738
Task: 33399
A few of our unit tests make API handlers return Mock objects. This
used to work with older WSME, but the current master has dropped
support for simplejson, which has apparently made validation stricter.
An example of resulting failures can be seen in RDO CI:
71833957b3_156a4cd0/mock.log
This change fixes it, also adding autospec=True to affected tests.
Change-Id: Ide4bc301d53ad81b53e5df8a9358cb65fdd8056c
The option [ilo]power_retry is deprecated at Stein, now it's time
to remove it from the tree.
Change-Id: I96d8e5141f170b6841250b2041ec775cc144f63f
Story: #2005673
Task: #30984
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/
devstack may be run as some other non-root user, and the service
will fail to start if there is no stack user available.
Change-Id: Ib1cfa6a1b0859a1e2680055ce0394053db1c307e
Signed-off-by: michaeltchapman <woppin@gmail.com>
It adds capability to the idrac driver for creating and deleting
RAID sets without rebooting the bare metal node.
Change-Id: I3f4282afff860d9771a3d37f4d5e1172d88e87a3
Story: 2004861
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
Pyghmi was moved from openstack namespace to the x
namespace. As such the devstack plugin needs to match
up otherwise devstack fails in CI to clone as cloning
is blocked if not in the projects list... Which it is,
as x/pyghmi.
Change-Id: I87bdf65dd2dac189642d0af6def2d0ed155f3c00
`hash_distribution_replicas` was deprecated in the Stein cycle (12.1.0).
Story: #1680160
Task: #30033
Change-Id: Iddc59ed113fb9808f8c8564433475638491be84f
Pushing too long messages in the node last_error and maintenance reason can
cause node.save() failures, leaving the node in a transient state, with no
conductor actually handling it anymore.
Change-Id: Id4db377781f83cf4d97564ced9622d5a8a8c67af
Story: #2005377
Task: #30359
Binding to 0.0.0.0 by default results in inability to work with IPv6,
which is a probable cause of Bifrost gate failures on some nodepool
providers. Using :: solves it.
Change-Id: Ic5c4c9b541c826ccf3025877f7c829fd34d0be6e
This fix binds the raid schema to draft-04 of the
json schema. The draft-04 is supported on both
jsonschema 2.6 and jsonschema 3.0.1.
Draft-06 and draft-07 require the schema change
which is incompatible with draft-04.
Story: #2005464
task: 30540
Change-Id: Ic30a0f18982f4da939f0f23eef8a233afea0e41a
The idrac hardware type requires python-dracclient versions greater than
or equal to 1.5.0 and less than 3.0.0.
This defines the upper bound to be less than 3.0.0 to make it easier to
backport to stable/stein. It was originally proposed against
stable/stein -- https://review.openstack.org/#/c/645956/ . Reviewers
asked that it be submitted against master first --
https://review.openstack.org/#/c/645956/1/driver-requirements.txt@12 --
and then backported to stable/stein.
The ironic master and stable/stein branches are compatible with
python-dracclient releases less than 3.0.0. Note that
python-dracclient's stable/stein branch was created off of tag 2.0.0.
The ironic stable/stein branch follows tag 12.1.0, which was created on
March 21. The python-dracclient tag 3.0.0 was created after that, on
April 4. The upper bound on master will be updated to less than 4.0.0 by
a follow-on change.
A related change has been proposed for stable/rocky --
https://review.openstack.org/#/c/651657/ . It will be backported to
stable/queens and prior after it merges.
Change-Id: I5f6d6be53aec9d72e8ba5cfa436f12e01966f871