Skip to content

Synchronise wallaby with upstream #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 13, 2024

Conversation

github-actions[bot]
Copy link

This PR contains a snapshot of wallaby from upstream.

If the node is locked, a lookup cannot be performed when an agent
token needs to be generated, which tends to error like this:

  ironic_python_agent.ironic_api_client [-] Failed looking up node
  with addresses '00:6f:bb:34:b3:4d,00:6f:bb:34:b3:4b' at
  https://172.22.0.2:6385. Error 409: Node
  c25e451b-d2fb-4168-b690-f15bc8365520 is locked by host 172.22.0.2,
  please retry after the current operation is completed..
  Check if inspection has completed.

Problem is, if we keep pounding on the door, we can actually worsen
the situation, and previously we would just just let tenacity
retry.

We will now hold for 30 seconds before proceeding, so we have
hopefully allowed the operation to complete.

Also fixes the error logging to help human's sanity.

Change-Id: I97d3e27e2adb731794a7746737d3788c6e7977a0
(cherry picked from commit 5ed520d)
(cherry picked from commit 06214d7)
@github-actions github-actions bot requested a review from a team as a code owner February 12, 2024 08:19
@github-actions github-actions bot added automated Automated action performed by GitHub Actions synchronisation labels Feb 12, 2024
@markgoddard markgoddard merged commit 733af27 into stackhpc/wallaby Feb 13, 2024
@markgoddard markgoddard deleted the upstream/wallaby-2024-02-12 branch February 13, 2024 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated Automated action performed by GitHub Actions synchronisation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants