sushy 3.7.2 release

meta:version: 3.7.2
meta:diff-start: -
meta:series: wallaby
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Iury Gregory Melo Ferreira <iurygregory@gmail.com>
meta:release:Commit: Iury Gregory Melo Ferreira <iurygregory@gmail.com>
meta:release:Change-Id: Ifd8fcc669a7c2761b1b6f33a8176241cb2a59c3d
meta:release:Code-Review+1: Dmitry Tantsur <dtantsur@protonmail.com>
meta:release:Code-Review+2: Thierry Carrez <thierry@openstack.org>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Workflow+1: Elod Illes <elod.illes@est.tech>

While testing on Python 3.10 two issues were spotted:
1) Missing formatting specifiers in registry logging
2) Reliance on the exact way HTTP status are converted to string

Fedora bug https://bugzilla.redhat.com/show_bug.cgi?id=1969148

Change-Id: I22d0033691ee0ba34fca14ac14904e33342a584a
(cherry picked from commit 5b38ec59)

Some vendors implement the original method of inserting and ejecting virtual media
using a PATCH request to the target URI
instead of using a POST request to the
insert_media and eject_media action URI.
Additionally the actions attribute might set to None
This implements the fallback method,
if there are no actions and the PATCH method is sent back in the Allow header

Change-Id: I2046c4e7c8739edd4aaac3e7facc378b82276ca4
(cherry picked from commit 9e5a1035)

This used to be set to application/json when there was request data,
but this was removed in change
I6bd9a0719acfb839fcf137c58bcf03254b1af5ad without any particular
explanation.

There have been reports of some redfish implementations returning
error responses (400 or 415) when this header is not set, specifically
HPE Gen9. It is good practice to always set Content-Type on requests
with data anyway. This change adds that header back.

Change-Id: I13107bbea4d422fdfe620ade735a2e150cb51bf2
(cherry picked from commit f52aac46)

Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/wallaby branch, tests will
continue to use the upper-constraints list on master.

Change-Id: Ieef76c74907986dd8ab3db6f8c71a30720819442

Change-Id: I55ab789b71159d19c8f31ace510b47c903b1a8e2

sushy 3.7.0 release

meta:version: 3.7.0
meta:diff-start: -
meta:series: wallaby
meta:release-type: release
meta:pypi: no
meta:first: no
meta:release:Author: Hervé Beraud <hberaud@redhat.com>
meta:release:Commit: Hervé Beraud <hberaud@redhat.com>
meta:release:Change-Id: I1e6ee139d84ec49ea331028818995f63513fa599
meta:release:Code-Review+1: Dmitry Tantsur <dtantsur@protonmail.com>
meta:release:Code-Review+1: likui <likui@yovole.com>
meta:release:Code-Review+2: Elod Illes <elod.illes@est.tech>
meta:release:Code-Review+1: Riccardo Pittau <elfosardo@gmail.com>
meta:release:Code-Review+1: Daniel Bengtsson <dbengt@redhat.com>
meta:release:Code-Review+2: Hervé Beraud <hberaud@redhat.com>
meta:release:Workflow+1: Hervé Beraud <hberaud@redhat.com>

Follow up to change Idd4158d87d27b6358c6d7a2a7183427a494ee384

Add wait method.
Rename TaskMonitor.get_task_monitor to TaskMonitor.from_response

Change-Id: I1b14bb1eddbf6eff82b0bd06e36c667bcaaf217d

Refactor TaskMonitor-s:
  - deprecate ``resources.task_monitor.TaskMonitor``
  - move TaskMonitor from ``resources.taskservice.taskmonitor``
    to ``taskmonitor``
  - add necessary methods from deprecated TaskMonitor to the
    moved one

Update Volume methods to use remaining TaskMonitor.

Add static helper method to TaskMonitor to initiate TaskMonitor
instance from response.
Replace TaskMonitor in connector with the remaining TaskMonitor.

Add method get_task_monitor to Sushy class. Deprecate
UpdateService.get_task_monitor.

Uppercase Location header in connector. While headers are case
insensitive, in unit tests where headers are mocked they are
case sensitive.

Change-Id: Idd4158d87d27b6358c6d7a2a7183427a494ee384

Similar to https://review.opendev.org/c/openstack/sushy/+/747960,
an ERROR is logged when the GET of this Redfish endpoint fails
prior to authentication, which causes concern for operators. Log
a debug message instead.

Change-Id: I70f7a6ecbbe72cfa7b0a46206de9cebbd5aef23e

Python 3.10 removes the deprecated aliases to collections abstract
base clases [1].

[1] - https://bugs.python.org/issue37324

Change-Id: I16eabdce9bb6e9303df8fb3baa48e490f4afa966

I have experienced this pretty often when testing secure boot
on Dell R430.

Story: #2008563
Task: #41702
Change-Id: I615e806196740af208ff7f68f814929a2fdc0332

Change-Id: Id35d5b3c1d09718d05f6b2e470412d76d60b5198

In the volume.py module, the first parameter passed to the TaskMonitor
constructor was incorrect. The parameter passed was the resource object
(self), but it should have been the connector object (self._conn). This
affected the create_volume() and delete_volume() methods.

The constructor calls were updated to provide the correct connector
parameter. And the unit tests were updated to test that the TaskMonitor
objects are successfully created.

Change-Id: I10e564185b4cd9faa24739766536d39646f8a7c1
Story: 2003514
Task: 41720

Change-Id: I2d082762fcf59d7b9bc8adc7c5159520ac628043

The minimum version since when tox accepts having inline comments
in deps is 3.9.0

https://tox.readthedocs.io/en/latest/changelog.html#v3-9-0-2019-04-17

Change-Id: I6e0b2bb4be15c67fa64a5a415e7814be9f8243f2

Change-Id: Ie006b57eddefb36c776bceab4708d46ac4e81e38

Story: #2008270
Task: #41582
Change-Id: I72f8103fe9bb4613ef8c53a3ff08a710dc96c12d

This patch fixes issue of redfish firmware update
for ilo5 based hardware by adding a new attribute
task_uri to monitor and validate the firmware
update since task_monitor uri does not provide the
appropriate response.

Change-Id: Ida1d314f77b9f114e572639c7ad46545be1ce962
Story: #2008403
Task: #41339

We need to specify doc requirements in doc/requirements.txt
to avoid problems with the pip resolver for the release team.
Removed specific doc requirements from test-requirements.txt

Change-Id: Ie401218013438b9de07d8dc9daa24485608b29a5

The supported_values property in the OperationApplyTimeSupportField
class returns an unmapped list of OperationApplyTime values supported
by the service. The convention in Sushy for properties that return a
list of schema-defined enumeration values is to return a
MappedListField. This type of field performs mapping between Redfish
schema-defined enumeration values and constants exposed by the Sushy
package.

This update adds the mapped_supported_values property to return a
MappedListField of OperationApplyTime values supported by the service.
The supported_values property is deprecated.

The create_volume method in the VolumeCollection class and the
delete_volume and initialize_volume methods in the Volume class are
updated to take optional apply_time and timeout keyword parameters.
This allows the caller of those volume methods to specify a preferred
OperationApplyTime annotation and a maximum timeout for synchronous
operations. If the specified apply_time is 'Immediate', the operation
is called with blocking enabled. Otherwise blocking is disabled. For
asynchronous operations, those three methods will now return a
TaskMonitor instance that the caller can use to monitor the state of
the task.

Change-Id: I8ba2b9ff1e80fa0c2edc3a11ab80844d732e4394
Story: 2003514
Task: 41087

As discussed during the upstream ironic community meeting on
Monday Dec 14 2020, the lower-constraints job is being removed.

Change-Id: Ie71603d57eef5f56f9a9fabac2a5283f472b135e

* move pep8 dependencies from test-requirements to tox.ini,
  they're not needed there and are hard to constraint properly.
* bump docutils required by sphinx

Change-Id: I349056b953878fa53ac43f37428e72411376038b