d3c3d4dabe
Or at least try to. Some deployments just don't use root device hints, and this is okay. However, other deployments need root device hints, and with fast track mode in ramdisks, we created a situation where the node cache could be updated by a human or software between the time the agent was started, and the deployment was requested. As a result, the agent has been updated to check if we have a hint and if we don't, update the cache from the node lookup endpoint. This is not needed when the inband deploy steps are executed, as the process of updating the steps does force the node cache to be updated. Change-Id: I27201319f31cdc01605a3c5ae9ef4b4218e4a3f6 Story: 2008039 Task: 40701
10 lines
422 B
YAML
10 lines
422 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue with nodes undergoing fast-track from introspection to
|
|
deployment where the agent internal cache of the node may be stale.
|
|
In particular, this can be observed if node does not honor a root device
|
|
hint which is saved to Ironic's API *after* the agent was started.
|
|
More information can be found in `story 2008039
|
|
<https://storyboard.openstack.org/#!/story/2008039>`_.
|