Skip to content

fix: retry on HTTP 503 from OpenBMC REST API instead of failing#7556

Merged
Obihoernchen merged 1 commit into
xcat2:masterfrom
VersatusHPC:fix/openbmc-503-retry
May 6, 2026
Merged

fix: retry on HTTP 503 from OpenBMC REST API instead of failing#7556
Obihoernchen merged 1 commit into
xcat2:masterfrom
VersatusHPC:fix/openbmc-503-retry

Conversation

@viniciusferrao
Copy link
Copy Markdown
Member

This PR adds some tolerance with non-responsive OpenBMC during transient status, as described on #4264.

OpenBMC BMCs sometimes return HTTP 503 when the REST service is busy or recovering from a reboot. xCAT reported the error and gave up, making the user retry manually. Second attempt usually worked.

When openbmc.pm gets a 503, retry the same request up to 3 times with a 3-second wait. If all retries fail, report the error as before. The existing 504 handling for bmcreboot is not touched.

Validation

IBM POWER9 AC922 (OpenBMC). No regressions.

Fixes #4264

OpenBMC BMCs intermittently return 503 Service Unavailable when the
REST service is busy or recovering. xCAT reported the error immediately,
requiring the user to manually retry. A second attempt usually succeeds.

Retry the same request up to 3 times with a 3-second wait on 503.
If all retries fail, report the error as before. The existing 504
handling for bmcreboot is preserved.

Ref: xcat2#4264
@Obihoernchen Obihoernchen modified the milestone: 2.18 May 6, 2026
@Obihoernchen Obihoernchen merged commit cb11564 into xcat2:master May 6, 2026
2 checks passed
@viniciusferrao viniciusferrao deleted the fix/openbmc-503-retry branch May 7, 2026 03:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rpower command intermittently reports 503 Service Unavailable Error

2 participants