Skip to content

[fm] Guard support bundle creation with SitrepGuardedInsert.#10535

Open
mergeconflict wants to merge 1 commit into
mergeconflict/fm-sitrepguardedinsert-alertsfrom
mergeconflict/fm-sitrepguardedinsert-support-bundles
Open

[fm] Guard support bundle creation with SitrepGuardedInsert.#10535
mergeconflict wants to merge 1 commit into
mergeconflict/fm-sitrepguardedinsert-alertsfrom
mergeconflict/fm-sitrepguardedinsert-support-bundles

Conversation

@mergeconflict
Copy link
Copy Markdown
Contributor

@mergeconflict mergeconflict commented Jun 2, 2026

Wire the support bundle resource through SitrepGuardedInsert:

  • impl SitrepGuardedResource for SupportBundle;
  • schema: support_bundle_generation on fm_sitrep and the rendezvous_support_bundle_created marker table (migration fm-bundle-resource-deletion);
  • support_bundle_create's FM path routes through the combinator, surfacing a stale sitrep as Error::Conflict;
  • SitrepBuilder tracks support_bundle_generation, bumping it when the outstanding support-bundle-request set changes; the closed-case carry-forward filter drops fully-satisfied closed cases and keeps those with unsatisfied support bundle requests;
  • fm_rendezvous reads the expected generation and aborts the support bundle loop on a stale mismatch; fm_analysis loads existing markers to drive carry-forward; omdb displays the new status fields and generation.

support_bundle_generation and alert_generation are tracked and guarded independently, so a stale generation for one resource aborts only that resource's rendezvous loop.

Context: #10248, builds on #10532 and #10533. Note, garbage collection for rendezvous_support_bundle_created rows is not in this PR, that should be coming later this week if all goes well.

@mergeconflict mergeconflict self-assigned this Jun 2, 2026
@mergeconflict mergeconflict added the fault-management Everything related to the fault-management initiative (RFD480 and others) label Jun 2, 2026
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-support-bundles branch from e15c2c1 to e5d67e2 Compare June 2, 2026 19:32
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-alerts branch from 1bc2f60 to 62cc3dd Compare June 2, 2026 19:32
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-support-bundles branch from e5d67e2 to 809d7d3 Compare June 2, 2026 19:50
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-alerts branch from 62cc3dd to 3d5af68 Compare June 2, 2026 19:50
@AlejandroME AlejandroME added this to the 21 milestone Jun 4, 2026
The support-bundle mirror of the preceding alert change: `impl
SitrepGuardedResource for SupportBundle`, the `support_bundle_generation`
column and `rendezvous_support_bundle_created` marker table (migration
fm-bundle-resource-deletion), `support_bundle_create`'s FM path routed
through the combinator inside its transaction, support-bundle generation
tracking and carry-forward, the fm_rendezvous bundle loop, the fm_analysis
bundle-marker lookup, and the omdb display.

`support_bundle_generation` and `alert_generation` are tracked and guarded
independently, so a stale generation for one resource aborts only that
resource's rendezvous loop.
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-support-bundles branch from 809d7d3 to 7128ff2 Compare June 4, 2026 20:56
@mergeconflict mergeconflict force-pushed the mergeconflict/fm-sitrepguardedinsert-alerts branch from 3d5af68 to a1beef9 Compare June 4, 2026 20:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fault-management Everything related to the fault-management initiative (RFD480 and others)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants