Skip to content

fix: skip disabled IPMI user slots in bmcsetup#7559

Merged
Obihoernchen merged 1 commit into
xcat2:masterfrom
VersatusHPC:fix/bmcsetup-disable-retry
May 7, 2026
Merged

fix: skip disabled IPMI user slots in bmcsetup#7559
Obihoernchen merged 1 commit into
xcat2:masterfrom
VersatusHPC:fix/bmcsetup-disable-retry

Conversation

@viniciusferrao
Copy link
Copy Markdown
Member

It was observed that bmcsetup currently walks every IPMI user slot and tries to disable each non-target slot. On Lenovo XCC, disabled or empty slots can return Invalid data field in request, so the script retries the same no-op command until timeout. With several disabled slots, that can add minutes to discovery and BMC setup, which is inefficient at best.

This change addresses the issue by reading the current IPMI user table first, removing the configured xCAT BMC user slot from the disable list, then disabling only non-target slots whose IPMI Msg flag is true.

If the user table cannot be read, the script falls back to the old behavior instead of silently skipping everything.

Fixes #5065

bmcsetup iterated every user slot and retried ipmitool user disable for slots that were already disabled. Lenovo XCC reports those attempts as Invalid data field in request, so discovery can spend minutes retrying no-op disables.

Read the current user table once per BMC, keep the old fallback when the table cannot be read, and disable only non-target slots whose IPMI Msg flag is true. Also use the loop's current username when resolving the target slot and keep the intended userslot 2 fallback assignment.

Fixes xcat2#5065
@Obihoernchen Obihoernchen added this to the 2.18 milestone May 7, 2026
@Obihoernchen Obihoernchen merged commit b227281 into xcat2:master May 7, 2026
2 checks passed
@viniciusferrao viniciusferrao deleted the fix/bmcsetup-disable-retry branch May 7, 2026 21:10
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.

bmcsetup bug

2 participants