While it's not entirely useless, it's extremely verbose and account
for 2/3 of ironic-api logs even when keystone is disabled.
Change-Id: I991d2af7eb6987830a5fa449026f43ac7a09fcff
The URIReference.is_valid method has been deprecated since rfc3986
1.1.0[1] and triggers the following deprecation warning.
DeprecationWarning: Please use rfc3986.validators.Validator instead.
This method will be eventually removed.
[1] https://github.com/python-hyper/rfc3986/commit/fd19bd90
Change-Id: I256e42b8aa736b278bab6b4aa145a859aca10e17
Add some notes on potential UDP packet loss during conductor/BMC
power sync with IPMI, the corresponding increase in retries and
how to mitigate.
Change-Id: I4bc9a8f6f7f4da7f719a65f76ae97b1244701ee9
This commit modifies curl option in wait_for_nova_resources to
bypass proxy with --noproxy option. Without this option, if you run
DevStack behind proxy, curl command fails with timeout &
wait_for_nova_resources also fails.
Because curl only accesses Placement service API, this modification
should be fair.
Change-Id: I5524a76594bb784f59be4d4e3970f72d4497891b
Generic way to configure clean step priorites feature
( https://review.opendev.org/c/openstack/ironic/+/744117 ) enabled support
for customising clean step priorities for any clean step by setting a
configuration option. However, due to an error in code, it was not possible
to use this feature to enable/disable steps entirely using this option
as overrides were applied too late, after the disabled steps were already
filtered out.
This change fixes this error, making it possible to use step priority
override configuration option to enable/disable steps as required.
Story: 2009105
Change-Id: If3c01e6e4e8cedfe053e78fab9632bfff3682b06
Apparently, connection to the agent can fail with
Unexpected error when processing next clean step.
SSLError: ('timed out',): ssl.SSLError: ('timed out',)
This change adds SSLError to retriable errors since most of them are
related to temporary conditions, and the certificate validation failure
is handled by requests separately.
Change-Id: I4805d410b4bc98196e77d8c44a217e363dc88f0a
* Instead of specifying the fields we want to oomit from create/get
subscription, now we are specifying the fields we want to be returned
(This will avoid problems when vendors are using different versions)
* When validating create_subscription are requiring that Context and
Protocol are present, use the default value from Redfish in case
they are not present in the Body request.
* When trying to delete a subscription that doesn't exist Ironic
returns 500 (default code from IronicException), this commit updates
the code to 404 to show that the subscription doesn't exist.
Change-Id: I81907be1ebc293118f5ffde4fd4d0485ade390df
The lower-constraints test was removed becuase of an issue where pip
could not correctly determine the required packages versions to install,
ending in an almost infinite loop that would end up in timeout, failure,
and general mayhem.
Recently the issue has been fixed and, if properly configured, the
lower-constraints test can provide good indication of which minimum
versions are required to support the current code.
This patch adds the test back to the current development branch.
The long term goal is to keep the lower-constraints file in the stable
branches, but remove the test job to avoid issues during backports.
Change-Id: I5fff32ec5dd1a045116bcf02349650b1f5e3a196
If this grep doesn't match, the task returns a failure and it causes
the job to abort with POST_FAILURE. I think more info is generally
helpful and you can always grep "netstat" on the file manually; thus
remove the grep to avoid suprious failure.
Change-Id: I189a0a8be25cb12e946d8ac58667b287f9698064
After commit d7a5b3469c the custom kernel
parameters are not used in cleaning/inspection. This patch fixes it.
Change-Id: Ic017cc0f3aebd4858a1a6e3326e5cf0fc0888d24
Explaing which cipher suites must be used and how to pre-configure the
BMC. Also explain the privilege levels.
Change-Id: I93845ac9dd068b0ddb52693afe4993804857e5ea
This patch adds two new vendor_passthru methods for Redfish:
- create_subscription (create a sbuscription)
- delete_subscription (delete a subscription)
- get_all_subscriptions (get all subscriptions on the node)
- get_subscription (get a single subscription)
Unit Tests in test_utils split into multiple classes to avoid random
failures due to cache.
Tested in bifrost env using two different HW:
- HPE EL8000 e910
- Dell R640
Story: #2009061
Task: #42854
Change-Id: I5b7fa99b0ee64ccdc0f62d9686df655082db3665
The devstack default limit enforcement for glance defaults
to 1GB, and unfortunately this is too small for many to use
larger images such as centos which includes hardware firmware
images for execution on baremetal where drivers need the vendor
blobs in order to load/run.
Sets ironic-base to 5GB, and updates examples accordingly.
Depends-On: https://review.opendev.org/c/openstack/devstack/+/801309
Change-Id: I41294eb571d07a270a69e5b816cdbad530749a94
Adds support to the ironic devstack plugin to configure
ironic to be used in a scope-enforcing mode in line with
the Secure RBAC effort. This change also defines two new
integration jobs *and* changes one of the existing
integration.
In these cases, we're testing functional crub interactions,
integration with nova, and integration with ironic-inspector.
As other services come online with their plugins and
devstack code being able to set the appropriate scope
enforcement configuration, we will be able to change the
overall operating default for all of ironic's jobs and
exclude the differences.
This effort identified issues in ironic-tempest-plugin,
tempest, devstack, and required plugin support in
ironic-inspector as well, and is ultimately required
to ensure we do not break the Secure RBAC.
Luckilly, it all works.
Change-Id: Ic40e47cb11a6b6e9915efcb12e7912861f25cae7
Add documentation for the CPU, memory, disk, and network burn-in
cleaning steps to the admin guide.
Change-Id: Ide8061f96eeb303490f06ebf31d2f2e6be93d0d1
Move the descriptions of the BIOS registry fields in the API to
a new section in the Redfish documentation.
Change-Id: Ifedb4526113bb84ccc598e13f5767b71a60f5532
Update minimum required versions of python packages.
The updates is based on crosscheck requirements from required
packages:
oslo-log 4.3.0 depends on oslo.context>=2.20.0
oslo-config 6.8.0 depends on rfc3986>=1.2.0
oslo-config 6.8.0 depends on requests>=2.18.0
oslo-log 4.3.0 depends on pbr>=3.1.1
oslo-log 4.3.0 depends on oslo.serialization>=2.25.0
oslo-policy 3.7.0 depends on oslo.context>=2.22.0
Also update minimum versions of ddt and stestr to avoid compatibility
issues with recent Python versions (3.8 and higher).
Change-Id: I34b558f4e7b93618130af1ba2250f6ab8575d4d6