Systems::get_power() returns a cached value
Bug #1663731 reported by
Hans Feldt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-redfish |
In Progress
|
Undecided
|
Unassigned | ||
Bug Description
Systems:
OS::Ironic integration since Ironic polls and waits for changes in power
state. With the current impl it will read a possibly stale cached value.
| Changed in python-redfish: | |
| status: | New → Triaged |
Revision history for this message
| Bruno Cornec (bruno-cornec) wrote | #1 |
| Changed in python-redfish: | |
| milestone: | none → 0.6 |
| Changed in python-redfish: | |
| status: | Triaged → Fix Committed |
| status: | Fix Committed → In Progress |
| Changed in python-redfish: | |
| assignee: | nobody → Sheikh Adilina (adilina) |
| assignee: | Sheikh Adilina (adilina) → nobody |
To post a comment you must log in.
We agree with the above.
From a library point of view, we think it should be more on the get_power() method.
get_power() --> Default behaviour could be to retrieve the cached value (provided by the first connection)
get_power(cache=no) --> Force to refresh the values.
Easiest implementation will be to refresh the class + subclass values , not only power.
Pros : we will avoid values discrepancies.
Cons: takes time to refresh (is it really an issue ?)