diff options
| author | Julia Kreger <juliaashleykreger@gmail.com> | 2020-08-11 13:13:09 -0700 |
|---|---|---|
| committer | Julia Kreger <juliaashleykreger@gmail.com> | 2020-08-11 13:13:09 -0700 |
| commit | 30d9cb47e62b62d570e1792515e16abf1ac3cd56 (patch) | |
| tree | 8d0708aceb8742b65a3e84e66ef40e6f1086bb12 /releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml | |
| parent | 84af06b19980e70cea920bfd55dd13981c846bb3 (diff) | |
| download | ironic-30d9cb47e62b62d570e1792515e16abf1ac3cd56.tar.gz | |
Handle an older agent with agent_token
Well, as the author of the agent token work, I could have
sworn we covered this case, but it seems not and agent commands
could fail.
What was occuring, when the token is optional, we were not backing
down on the agent client and failing even though we could detect
the failure and handle it accordingly.
Change-Id: Ibd7e17fb00747485c8072289fff9b28d4da17c39
Story: 2008002
Task: 40649
Diffstat (limited to 'releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml')
| -rw-r--r-- | releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml b/releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml new file mode 100644 index 000000000..babe89da5 --- /dev/null +++ b/releasenotes/notes/handle-older-agent-command-5930124fd03bb327.yaml @@ -0,0 +1,6 @@ +--- +fixes: + - | + Fixes an issue with agent token handling where the agent has not been + upgraded resulting in an AgentAPIError, when the token is not required. + The conductor now retries without sending an agent token. |