For HPE Gen10 servers we are not able to receive consistent response
while accessing the System with id: "/redfish/v1/Systems/1".
The reason was related to multiple Sushy object creation which in
turn will create multiple active sessions for the same Redfish
controller at any given point.
Instead of using session based authentication (the default behaviour
in Sushy) we use basic authentication at the time of Sushy object
creation. This fixes the session issue for Gen10 servers.
Change-Id: Ic13da26a77863f8c383fa8ba185e05a8fc2e9fcf
Closes-Bug: #1764395
(cherry picked from commit da0c7b3db906f375f1f09a31433f46b1c553c95f)
Reviewed: https:/ /review. opendev. org/656561 /git.openstack. org/cgit/ x/proliantutils /commit/ ?id=5bdde1ba891 0436beaf973c0d8 6509d1dc86015e
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit 5bdde1ba8910436 beaf973c0d86509 d1dc86015e
Author: mvpnitesh <email address hidden>
Date: Fri Apr 13 10:26:54 2018 +0000
Fixes session issue for Gen10 servers
For HPE Gen10 servers we are not able to receive consistent response v1/Systems/ 1".
while accessing the System with id: "/redfish/
The reason was related to multiple Sushy object creation which in
turn will create multiple active sessions for the same Redfish
controller at any given point.
Instead of using session based authentication (the default behaviour
in Sushy) we use basic authentication at the time of Sushy object
creation. This fixes the session issue for Gen10 servers.
Change-Id: Ic13da26a77863f 8c383fa8ba185e0 5a8fc2e9fcf 5f1f09a31433f46 b1c553c95f)
Closes-Bug: #1764395
(cherry picked from commit da0c7b3db906f37