ironic-tempest-partition-uefi-redfish-vmedia was renamed to
ironic-tempest-uefi-redfish-vmedia a long time ago
Change-Id: Iaa63e9cf12d47667955973033586fa65dd18e6b7
Long story short, in some circles the EFI grub network boot
over http with VMs is regarded as unstable. What appears to
be happening, with service logs at least, is we get a HEAD
request (grub code always issues a HEAD request first to minimize
memory usage), and then re-requests the file contents.
So what we end up seeing on the grub side is:
error: Fail to receive a response! status=104
error: Fail to send a request! status=0x800000000000000f.
What appears to happen is things get gumed up in firmware and
the generally that means we can't run this test in CI.
Change-Id: I1471c9429b742abb250b9a3a910108f1711ad574
* Remove @Redfish.Copyright, it's not an allowed field.
* Remove unused fields such as AssetTag.
* Mark fields used in inspection and other optional features as
optional.
* Add missing VirtualMedia on System and VirtualMedia fields.
* Add missing Thermal information and its subresources.
* Clarify which fields on System are links.
* Add Purpose field to all fields and actions.
* Expand the BIOS object with the actual requirements.
* Add ServiceRoot and services we use.
* Add missing resources related to RAID.
Change-Id: I35f8f49e4c70e736b685c3eeebf79326592b6314
This commit introduces support for provisioning ARM (aarch64)
fake-bare-metal VMs in Ironic for the purpose of eventually supporting
CI testing on ARM64 architecture-based hardware.
Change-Id: Ie4bff8892228275ad0fb940c30e8071f7f4c423f
Python regexes are deprecated in Zuul, so this commit updates the
configuration to use RE2-compatible syntax.
Change-Id: If4973be103076f5a3879dc630e104d129377f7da
The functional test job needs neutron for neutron dependent
tests to be able to execute. As such RabbitMQ and Neutron
are enabled for the functional test job at this time.
Change-Id: I04f76ca1570b969136c0922eb07bc85360369920
Changing the ironic-tempest-uefi-redfish-vmedia and
ironic-tempest-ovn-uefi-ipmi-pxe jobs to only run
tempest test_baremetal_server_ops_wholedisk_image.
We saw failures on the partition tests for this jobs.
Related-Bug: #2057972
Change-Id: I2e26d7955ade11046bf89b6f4c9c2c4f16da1574
Adds a job which utilizes the redfish-https boot mechanism
code which recently landed in ironic, which operates similar
to virtual media
Change-Id: Iad55a263ed34e6b121495b72a3c79449d7471901
* Adds httpboot enabled CI
Sets the interfaces to be enabled on the standalone job
in anticipation for standalone job support for these
interfaces[0] and switches the boot from volume
job over to utilize httpboot by default.
* Phases out now-redundant ironic-standalone job
The ironic-standalone job does all the same work as the
ironic-standalone-redfish job, and IPMI CI jobs are covering
IPMI cases. So we don't need this anymore.
Also makes a note on another redfish job which is likely
redundant as well, although does not yet remove it.
* Fix IPMI Partition Job name
This is more of a test of OVN than of partition specifically,
in fact, it runs both wholedisk and partition jobs already. Make
the name more sensible.
[0]: https://review.opendev.org/c/openstack/ironic-tempest-plugin/+/902171
Co-Authored-By: Julia Kreger <juliaashleykreger@gmail.com>
Change-Id: I6c41b8f124e2e1fbc314243bf821153d79e2e09b
DNSMasq is not cooperating with us; it's respawning frequently.
Temporarily make these non-voting while we troubleshoot.
Change-Id: I0dcb09f31254d81d3a5ec9a52304bab93901e8f6
dnsmasq-2.86 shipped in Ubuntu jammy has a
known issue[1] which is fixed in dnsmasq-2.87
but it's not yet released with Ubuntu jammy.
Until fixed version is available in Ubuntu
jammy let's use source install instead of
using a older version from Ubuntu focal.
[1] https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2022q3/016562.html
Update from Julia:
Pushing forward the source fix again as ubuntu removed the
prior path we were using as a focal package and replaced
it with a package which is demonstrating the same basic issue.
Related-Bug: #2026757
Change-Id: I7ffcd167fc1e3a8c1192d766743bb5620d85ef35
Third in a series of commits to add Codespell to Ironic Repos. This commit adds the Tox Target to CI
A future commit could potentially add a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: I82239bd5ca1b184e36c63d08413362c76fa8d4b4
The following services were removed some time ago.
- nova-objectstore
- nova-consoleauth
- glance-registry
Change-Id: I3a577c44abe46fc6cb146f3540bded1c5cb4a511
Change the default RBAC policy in ironic such that the new RBAC
policy is enforced by default and the legacy policy is not usable
unless explicitly re-enabled.
Depends-On: https://review.opendev.org/c/openstack/metalsmith/+/905012
Change-Id: Id559f1d8b9a76c8a570b598585c2d58c56d08837
The host currently hard-coded is not functioning. This replaces
the hard-coded mirror by the local CI mirror detected. In case
mirror info is not available then upstream centos mirror is used.
Change-Id: I96a8cb45154c9dbb50efecc22d34c4ff75c6722a
The standalone job has not passed on the master branch in a
very long time. I stopped looking at the history as of August 2023,
but it was only passing on Xena and Wallaby stable branches.
A few things to note:
* It appears to be intended to exercise inspector as a WSGI app,
and loads quite a bit of different configuration.
* Overall, it is failing due to the image it is trying to use
(cirros) which doesn't support setting a bootloader up, but
that is sort of required.
* Job is configured to netboot a node for an OS on the disk,
but that is not something ironic does really anymore. Quite
possibly, that is why the job is failing.
* Inspector, as a non-integrated thing, is on the path of
deprecation at this point, so we don't really need to focus
on this specific case anymore.
Overall, it seems like a job we should have just removed some
time ago. So... doing so.
Change-Id: I3aca63c183af863d9db1f27a4cfe0d6495bb03c2
Bandit 1.7.5 introduced some changes which broke the bandit job,
which caused the job to fail ages ago. We've since fixed those.
But, moving forward we need to fix these relatively quickly when
they occur, as such changing the test to voting improves our overall
security posture by forcing us to address these as they occur.
Change-Id: I4a7954bfd20eafdb578896e1f61204edc7f9ec7e
Two jobs are changed to test a reduced Redfish implementation:
one PXE job uses the minimum version (only boot/power management)
one vmedia job uses the reduced version (+ NICs, virtual media)
Change-Id: Ib3afdb26b9cd36c0e4f3d736b9c69a5bf508fc0e
This reverts commit 6ffef5b165d78508f8ebd2fc5e94d95d3ac27e51.
Reason for revert: We have the fix in nova, when it merges we can revert the BFV job to voting
Depends-On: https://review.opendev.org/c/openstack/nova/+/903324
Change-Id: Iadee0d696b13ecfe6f93c241b3f9e59be66f6f43