When reconfiguring BIOS on iDRAC nodes, there can be a conflict between
Lifecycle Controller job implementing the actual BIOS change and another
job implementing boot sequence override. This change resolves the issue
with the exception handler by adding code dealing with HTTP 409 error
which wasn't correctly handled before, causing the problem.
Change-Id: Ib57a330d267f573c8481e4823b0f5ee14556fde3
Currently, get_unfinished_jobs() returns jobs in Running and Scheduled
states but not Paused state. This causes problems, because a job in
Paused state will still block more instances of the same job from being
created. This change adds jobs in Paused state to this function's
output. It also migrates states indicating that job hasn't finished
to a constant.
Change-Id: I617b7427704aba7bc6cbaa4384906598f9d4e408
Currently, the requirement of having Id field set is triggering
MissingAttribute exceptions. Removing this code doesn't seem to be
causing any issues.
Change-Id: I827ef12b48767b8491106e25e85a71a220a99505
This is a 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: Ic9fbc911b9af557be1bb1a7741e0409fcd09406e
Can determine controller's mode and convert to RAID mode for
eligible controllers (PERC 9 and PERC 10).
Depends-On: https://review.opendev.org/c/openstack/sushy/+/850899
Change-Id: I492c476c6d69b458449eed69644b051b66dfdc65
We have updated the yoga testing runtime to keep the
py36 testing.
- https://review.opendev.org/c/openstack/governance/+/820195
Unit tests job template is also updated to keep python
3.6 as a voting job. So with the py3.6 and py3.9 testing as voting
job template, we are keeping python 3.6, 3.7, 3.8, and 3.9 as
tested versions in the Yoga cycle.
- https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/820286
This commit re-add the python 3.6/3.7 versions in setup.cfg classifier.
Change-Id: Iaf69ad23ccf85b3a92d89b46a8c4726b3f38ce8f
New optional parameter added to export configuration method to control
if destructive iDRAC settings, such as those that could cause loss of
network access, are exported. It is also unlikely that these fields
are necessary during import to replicate same static IP address
settings. User can still put these fields back during import.
Change-Id: Iad39267fedf1c1a7381d03152eb0cea0c114eede
BOSS controllers do not support clearing foreign config.
Requesting to do so results in HTTP 400 Bad Request response.
Change-Id: I6b8f0a97e73dafc3b130e79769f3391dc0061999
Newer iDRAC firmware has changed how it reports
IncludeInExport@Redfish.AllowableValues, no longer including
comma separated option. Although iDRAC violates AllowableValues
validation logic, need to work around this.
Change-Id: I21524bef52e32eb56c105bb57c8f846503a401f4
Introduces System OEM extension and Dell RAID service
with first Convert to RAID/Non-RAID methods.
Depends-On: https://review.opendev.org/c/openstack/sushy/+/799504
Change-Id: I53964f935d82c349d51c0991c46a3e2b9b0d2682
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:
UserWarning: Usage of dash-separated 'description-file' will not be
supported in future versions. Please use the underscore name
'description_file' instead
[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb
Change-Id: Ib392d89aded3c0f639036bb47739d10f5396a346
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I2e6521c9f0c6a0885692edc485659b420828a2d2
