Apparently, some HPE Gen 10 Plus machines do not allow identity encoding
when BIOS registries are requested. Add a fallback to Connector.
Change-Id: I7363df5f5f74705307990dda9dfc7baebd5c07a3
- the names of the parameters and annotations did not match, so this was fixed.
Change-Id: Ib06a264dfc72f2854ad49bc08a11b324f4981ee3
Signed-off-by: Youngjun <yj.yoo@okestro.com>
Add file to the reno documentation build to show release notes for
stable/2024.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2024.1.
Sem-Ver: feature
Change-Id: If76d8a07d4bbb4c4330ee7431764c89a5868df23
The tox deps option grants installation of single dependencies and
requirements, optionally pinned using constraints, before installing
a package, therefore not granting installation of the correct
constraint during the package installation.
To fix that tox 4.4.0 has introduced the constrain_package_deps
option [1]
[1] https://tox.wiki/en/4.12.1/faq.html#using-constraint-files
Change-Id: I3a9e4748c1cd7aad4c88809b9d3652471b7a3e0d
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: Ia7662fa159472119201bcd7c5c01982139bdeb38
Second in a series of commits to add Codespell to Ironic Repos. This one adds the command that was used to fix the spelling errors.
Future Commits will add CI support and potentially a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: Ib439c9873d601bb140bd3f97acb5ee2d551c7063
This is the first in a series of commits to add support for codespell. This is continuning the process completed in ironic-python-agent.
Future Commits will add a Tox Target, CI support and potentially a git-blame-ignore-revs file if their are lots of spelling mistakes that could clutter git blame.
Change-Id: I305a44beb929495f4b67a5e94b0387647814db1e
After DMTF release a new version of their guide[1], there was an
update in VirtualMedia URI.
Deprecated: /redfish/v1/Managers/{ManagerId}/VirtualMedia/{VirtualMediaId} New:
/redfish/v1/Systems/{ComputerSystemId}/VirtualMedia/{VirtualMediaId}
So, it is needed that System has access to VirtualMedia in Sushy lib
to later Ironic may be able to handle this. This way, i added a
property in System that it can have access to VirtualMedia instance.
[1]https://www.dmtf.org/sites/default/files/standards/documents/DSP2046_2023.2.pdf
Partial-Bug: #2039458
Change-Id: I7bd7db539eab158c283524aecdaa9ebebd033cf6
Currently, no handling is done for the 2nd request (we catch HTTPError,
but it won't be raised without raise_for_exceptions). Recurse into
the same call instead.
Change-Id: I9d593a741344fd7d5d6d59eca48a12222572c1ce
According to bug https://bugs.launchpad.net/sushy/+bug/2028214
the 2.15 value in the error string we had recorded for iLO devices,
is actually a version indicator according to one of the ilo developers.
Closes-Bug: 2028214
Related-Bug: 2021995
Change-Id: I0059341e3815f2d13bdaf1efa794e29a6f2cd503
Add the indicator for boot progress, as mapped to the System
``BootProgress`` field and subvalues, which allows for API
consumers to determine the current status.
Related-Bug: #2041902
Change-Id: Icaf8d1ba1a46ab5ffbf8a98fc7eff020fdcecfa5
In order to utilize Http Boot from URL, we need to be
able to set the the parameter to the remote BMC.
This enables a greater level of security as the
URL and ultimately the instruction comes from an
authenticated source, i.e. the BMC connection, and
not DHCP which is the fallback if a target is set
to UefiHttp.
We now also unset the the http boot uri if it is set
and we're not setting an explicit URI to use. This
keeps the state of the data clean in order to prevent
any unexpected behavior.
Change-Id: I73ae614ffe735bd055090ded32926a5416a12fc0
Some Redfish implementations require current ETag of Redfish
resource against which resource update is requested to be
included in HTTP PATCH operation header.
This commit adds missing ETag in PATCH operation header.
Change-Id: I3f88d8a7032fd9071aa033c706768127da1d12af
Add file to the reno documentation build to show release notes for
stable/2023.2.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.2.
Sem-Ver: feature
Change-Id: I1fda62003a2b703a347aa2b05db9d7bcb449d46f
_get_registry method of ResourceBase retrieves
Registry-like resource specified by identity
parameter of _get_registry.
However current _get_registry method of ResourceBase
retrieves Registry-like resource whose name is in
_attribute_registry. This works with Bios resource
but doesn't with another resource. This commit fixes
this.
Change-Id: Ifd01b5f633cb5076abb09a13c223b19f07e68fe6
Before this change, a request to a nonresponsive BMC may have hung
forever waiting for requests to connect and read. Now, we ensure all
calls have a timeout unless explicitly disabled by the API user.
Because timeout was already an argument for _op, anyone attempting
to previously override the requests timeout (send one at all) wouldn't
have been able to for pythonic reasons.
Closes-Bug: 2021995
Change-Id: I76c543c6e39bab81f46a7aa00f1d38328c30cf7b
The Cisco CIMC 4.1(2b) and potentially others do not
set the Location header as required by the Redfish
standard on a successful login, but return a session
object as a body.
By taking the session-uri out of the body,
we avoid leaking sessions in that situation.
Story: 2010477
Task: 47038
Change-Id: I3dbf80f3383c51d3e754516529471698851bf573
This not great patch allows us to automatically retry when we
encounter a message from the BMC indicating that the requested
operation was invalid.
We've seen similar issues on other BMCs in the past, however
in this case the BMC uses a HTTP 400 error as opposed to a 500
error. It is not perfect, but easily accounted for with
differing approaches to the client being aware or not of the
underlying state.
Change-Id: Ib78198a60a8924de934bda0c9a0b9298541496cf
Closes-Bug: #2016307
This commit adds the TransferMethod to insertmedia
calls if necessary.
Some HW require that the TransferMethod is set before
inserting virtual media.
Change-Id: I7fc5d41cdcf79d61cb1906f2755f55f284efe766
Some tests tool and IDE may create a .local directory inside the repo
with virtualenvs for dependencies, other tools may create . directories
or files for temporary reports.
While they can be removed in a second time, or configured differently,
it's advisable to just exclude all file starting with . from the
flake8 tests to avoid confusion and possible unexpected errors.
Change-Id: I6fdee20603437773c8a8c08cce3bbdcb4f8ef0e7
Add file to the reno documentation build to show release notes for
stable/2023.1.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/2023.1.
Sem-Ver: feature
Change-Id: Ib2998dc14dba7a7a99c827dd7b5180f383700759
The default value for language in sushy is "en",
in the ZT hardware some registries have "en-US"
as their language, in this case we can't get the
right information.
This commits changes the logic to accept the case
where the registry language starts with the default.
Change-Id: I0c4690925d086af593a691565a66ce90c19be156
if the env REQUESTS_CA_BUNDLE is set the requests.Session() ignores the
verify parameter. Therefore the verify parameter is moved directly into
the function call of request.
Workaround for https://github.com/psf/requests/issues/3829
Change-Id: I66dc7c4d90e5bd5e3d1b331cf1728f27dece6dd4
- Remove skipsdist that it was never supported and causes breakage
when used with usedevelop.
- disable setuptools autodiscovery
Change-Id: Iee925dd901d3b7e3407e9d2356b5d7b81d17fc55
Connector is not created with every request, but long-lived.
As the result retries run out when using sushy for longer
and resulting in permanent failure where another retry or so
should be enough. Fix this by counting retries per request.
Also fix and update log message for clarity.
Change-Id: I879b0410fd1f2f42657517c2ae435dd4681f8c8d