ironic-python-agent/releasenotes/notes/understand-node-conflict-is-locked-2ea21dd45abfe4f7.yaml
Jay Faulkner 36e5993a04 [codespell] Fix spelling issues in IPA
This fixes several spelling issues identified by codepsell. In some
cases, I may have manually modified a line to make the output more clear
or to correct grammatical issues which were obvious in the codespell
output.

Later changes in this chain will provide the codespell config used to
generate this, as well as adding this commit's SHA, once landed, to a
.git-blame-ignore-revs file to ensure it will not pollute git historys
for modern clients.

Related-Bug: 2047654
Change-Id: I240cf8484865c9b748ceb51f3c7b9fd973cb5ada
2023-12-28 10:54:46 -08:00

14 lines
699 B
YAML

---
fixes:
- |
Fixes, or at least lessens the case where a running Ironic agent can stack
up numerous lookup requests against an Ironic deployment when a node is
locked. In particular, this is because the lookup also drives generation of
the agent token, which requires the conductor to allocate a worker, and
generate the token, and return the result to the API client.
Ironic's retry logic will now wait up to ``60`` seconds, and if an HTTP
Conflict (409) message is received, the agent will automatically pause
lookup operations for thirty seconds as opposed continue to attempt
lookups which could create more work for the Ironic deployment
needlessly.