diff options
| author | Dmitry Tantsur <dtantsur@protonmail.com> | 2020-10-06 17:44:07 +0200 |
|---|---|---|
| committer | Dmitry Tantsur <dtantsur@protonmail.com> | 2021-12-06 12:38:04 +0100 |
| commit | 18d016f7961e8dcac851ae099d63c93a227ac992 (patch) | |
| tree | f3a23e1947efc7f45c46ee374db6612719e43b57 /releasenotes | |
| parent | e51c6b930e1e0c64de8f233417a686a24d24de49 (diff) | |
| download | ironic-18d016f7961e8dcac851ae099d63c93a227ac992.tar.gz | |
Avoid RPC notify_conductor_resume_{deploy,clean} in agent_base
Currently we use an RPC call to the conductor itself to proceed to the
next clean or deploy step. This is unnecessary and requires temporary
lifting the lock, potentially causing race conditions.
This change makes the agent code use continue_node_{deploy,clean}
directly. The drivers still need updating, it will be done later.
Story: #2008167
Task: #40922
Change-Id: If4763d542029b9021432425532f24a0228f04c25
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/no-deploy-rpc-dec8ee1d0326d1ad.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/no-deploy-rpc-dec8ee1d0326d1ad.yaml b/releasenotes/notes/no-deploy-rpc-dec8ee1d0326d1ad.yaml new file mode 100644 index 000000000..74f333b48 --- /dev/null +++ b/releasenotes/notes/no-deploy-rpc-dec8ee1d0326d1ad.yaml @@ -0,0 +1,5 @@ +--- +other: + - | + The agent deploy and cleaning code no longer uses an RPC call to the same + conductor when proceeding to the next deploy or clean step. |