We have some drivers, such as SNMP, which do not support metrics.
Environments with these nodes should not get "N" messages for "N" nodes
that can't generate sensor data.
Closes-bug: 2047709
Change-Id: Ibc1f3feb055521214512c8b350d67933491c2550
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
Automated cleaning is not guaranteed to be enabled, and in any case it's
too late to cache the components at that point: firwmare upgrades may
happen before the transition to "available".
Change-Id: I6b74970fffcc150c167830bef195f284a8c6f197
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
This commit removes 'VolumeType' which param has long been
deprecated in DMTF Redfish schema, also removes 'Encrypted'
param as per discussion, and places 'Drives' inside 'Links'
as per the new DMTF schema.
Closes-Bug: 2045645
Change-Id: I91d2decab19e352ca3560227d17acfaa1a1dca94
First, it tries to create components even if the current version is not
known and fails with a database constraint error (because the initial
version cannot be NULL). Can be reproduced with sushy-tools before
37f118237a
Second, unexpected exceptions are not handled in the caching code, so
any of them will cause the node to get stuck in cleaning forever.
On top of that, the caching code is missing a metrics decorator.
This change does not update any unit tests because none currently exist.
Change-Id: Iaa242ca6aa6138fcdaaf63b763708e2f1e559cb0
Our validation does not expect a host-port pair, not having colons in
the hostname. We don't need to verify all possible cases: we will return
404 for a conductor that does not exist.
Change-Id: Iea65575f540a89a0de280fb730e430647c5733dc
Use the 'volume_name' field from the logical_disk in the
target_raid_config field of a node, instead of just 'name' (which is
incorrect as per the Ironic API expectation), to create the RAID volume
Change-Id: Ib8b2589d91be67a848411ab6be852bcb4de58bc7
Reorganize the existing docs to give space to more information.
Cover the most critical topics, except for installation.
Change-Id: If0f185e0303d6f8071306edbc64b9c5704f58d16
At least on some Dell machines, the Redfish SecureBoot resource is
unavailable during configuration, GET requests return HTTP 503.
Sushy does retry these, but not for long enough (the error message
suggests at least 30 seconds, which would be too much to just integrate
in Sushy). This change treats internal errors the same way as
mismatching "enabled" value, i.e. just waits.
Change-Id: I676f48de6b6195a69ea76b4e8b45a034220db2fa
This commit:
- fixes a few nits that were pointed out after the feature
was merged
- doesn't affect the functionality of the feature
Closes-Bug: #2021947
Change-Id: I1dd024b9994df2b367f61cea75eb71fabe57abfd
tl;dr, devstack no longer supports focal, and now errors which
results in the job failing.
Also changes the snmp job to utilize the test_ramdisk_iso
feature, as *opposed* to a full deployment because iPXE
shipped with Ubuntu no longer likes to chain boot in UEFI
mode to a block device. The easiest path, is just to run
a ramdisk in that case, which also sort of mirrors what
users of the SNMP power interface *tend* to do.
Related-Bug: #2034588
Change-Id: I276885b8f0492ead8cea38fe13826123131984ea
Object create/delete operations translate clearly from swiftclient to
the SDK. Switching the temp URL handling is a little more disruptive but
the result is slightly more centralized and enables key rotation.
Change-Id: I8df2f032224bd5e540139a798a7ab76a1aeebb06
Closes-Bug: #2042493
We fixed a bug in wsgi_service around cleaningo up unix sockets; we
should document the fix in a release note.
Change-Id: I6ecb489ea1a9e6490c5ddca5c7467b0c4324dfd1
Currently, it logs a lot of entries without context, which won't be
readable when several nodes are deployed at the same time, nor when
someone greps for a node UUID.
Make fewer log entries and add node UUID for context.
While here, modernize the code a bit.
Change-Id: I3a840e47a09e77a9f8d35a7cf400c4bdd4111f91
