8a64d03dc0
Fixes redfish hardware type to cache and reuse `Sushy` objects when talking to BMC. Prior to this fix redfish hardware type never reused authenticated HTTP sessions (tokens) e.g. effectively created new HTTP session on every BMC call. That may have led sometimes to session pool exhaustion with some BMC implementations. To properly terminate authenticated session, sushy has to make an explicit DELETE call against BMC Redfish Session API. As of this commit, sushy does not do that so that ironic could still exhaust BMC sessions. However, the likelihood of running out of BMC sessions seems to be lower with this fix considering lesser frequency of new sessions creation. The proper fix would be to make sushy terminating authenticated session with BMC on `Sushy` object deallocation. Change-Id: I18ea013fd6e07c98b8c47d95772d3129132cdc53 Story: 2003813 Task: 26566 |
||
|---|---|---|
| .. | ||
| notes | ||
| source | ||