Skip to content

feat(ironic): configure SNMPv3 user through runbooks - #2618

Merged
cardoe merged 2 commits into
mainfrom
enable-obm-monitoring
Nov 2, 2026
Merged

cardoe merged 2 commits into
mainfrom
enable-obm-monitoring

Conversation

@haseebsyed12

@haseebsyed12 haseebsyed12 commented Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

What does this change do?

Adds the configure-snmpv3-user --node <name-or-uuid> command and the bmc-configure-snmpv3-user Argo WorkflowTemplate to configure monitoring on existing baremetal nodes through the Ironic runbook, without re-enrollment.

The workflow selects the operation from the node's current state:

  • manageable: run the runbook through manual cleaning and return to manageable.
  • active: run the runbook through servicing and return to active.
  • available: save the original automated-cleaning policy, disable automated cleaning, move to manageable, run the runbook, then return to available and restore the policy.

The runbook must disable the ramdisk and have a matching node trait. Nodes in maintenance or unsupported provisioning states are rejected before starting the operation.

The workflow waits for busy nodes, retries HTTP 409 conflicts on individual mutations, and rechecks state before each attempt. A per-node Argo mutex serializes workflows using the same mutex. Interrupted operations retain the saved cleaning policy so a later run can restore it safely. Runbook errors are reported even when Ironic returns the node to the expected stable state.

Upgrade impact

  • This change requires operator action to upgrade.

The workflow uses the existing bmc-configure-snmpv3-user Ironic runbook and baremetal-manage OpenStack credentials. The runbook must be present with the required traits and ramdisk disabled before invoking the workflow.

@haseebsyed12 haseebsyed12 changed the title feat(ironic): allow automation to configure SNMPv3 user independently of the node's provisioning lifecycle using vendor passthru feat(ironic): configure SNMPv3 user using vendor passthru Oct 30, 2026
@github-actions

github-actions Bot commented Oct 30, 2026 •

Copy link
Copy Markdown

Python test results

63 tests   63 ✅  7s ⏱️
 1 suites   0 💤
 1 files     0 ❌

Results for commit c2d16f7.

♻️ This comment has been updated with latest results.

@haseebsyed12
haseebsyed12 force-pushed the enable-obm-monitoring branch 2 times, most recently from fe821bb to 52ab62b Compare October 30, 2026 14:15
@haseebsyed12
haseebsyed12 requested a review from a team October 30, 2026 15:50
@haseebsyed12
haseebsyed12 marked this pull request as ready for review October 30, 2026 15:51
@haseebsyed12
haseebsyed12 force-pushed the enable-obm-monitoring branch from 9644790 to abfbc78 Compare October 30, 2026 15:53
… of the node's provisioning lifecycle using vendor passthru
@haseebsyed12
haseebsyed12 force-pushed the enable-obm-monitoring branch 4 times, most recently from 08b86d1 to 3121abc Compare November 2, 2026 13:21
@haseebsyed12 haseebsyed12 changed the title feat(ironic): configure SNMPv3 user using vendor passthru feat(ironic): configure SNMPv3 user through runbooks Nov 2, 2026
@haseebsyed12
haseebsyed12 force-pushed the enable-obm-monitoring branch from 3121abc to 002a1d8 Compare November 2, 2026 14:18
@haseebsyed12
haseebsyed12 force-pushed the enable-obm-monitoring branch from 002a1d8 to c2d16f7 Compare November 2, 2026 15:42
@cardoe
cardoe added this pull request to the merge queue Nov 2, 2026
Merged via the queue into main with commit cc347dc Nov 2, 2026
71 checks passed
@cardoe
cardoe deleted the enable-obm-monitoring branch November 2, 2026 15:52
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.

3 participants