Skip to content

[reconfigurator-planning] clear remove-mupdate-override from blueprint even if no target release is set#9082

Merged
sunshowers merged 2 commits into
mainfrom
sunshowers/spr/reconfigurator-planning-clear-remove-mupdate-override-from-blueprint-even-if-no-target-release-is-set
Sep 24, 2025
Merged

[reconfigurator-planning] clear remove-mupdate-override from blueprint even if no target release is set#9082
sunshowers merged 2 commits into
mainfrom
sunshowers/spr/reconfigurator-planning-clear-remove-mupdate-override-from-blueprint-even-if-no-target-release-is-set

Conversation

@sunshowers

Copy link
Copy Markdown
Contributor

Currently:

  • if a target release is set, we go ahead and clear the remove-mupdate-override instruction from blueprints, regardless of whether artifacts match
  • if no target release is set, we don't do that

This behavior is inconsistent. We shouldn't gate the mupdate override part of the state machine on a target release not being set.

Created using spr 1.3.6-beta.1
Comment on lines 196 to 198
DNS zone: "control-plane.oxide.internal" (unchanged)
unchanged names: 51 (records: 65)
unchanged names: 52 (records: 68)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is being fixed separately, I believe -- it's here to make tests pass.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think this is broken on main. But probably fine to just land this PR to fix it?

Created using spr 1.3.6-beta.1
Comment on lines 196 to 198
DNS zone: "control-plane.oxide.internal" (unchanged)
unchanged names: 51 (records: 65)
unchanged names: 52 (records: 68)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think this is broken on main. But probably fine to just land this PR to fix it?

@sunshowers sunshowers enabled auto-merge (squash) September 24, 2025 21:22
@sunshowers sunshowers merged commit 65c8aed into main Sep 24, 2025
17 checks passed
@sunshowers sunshowers deleted the sunshowers/spr/reconfigurator-planning-clear-remove-mupdate-override-from-blueprint-even-if-no-target-release-is-set branch September 24, 2025 23:01
leftwo pushed a commit that referenced this pull request Sep 26, 2025
…t even if no target release is set (#9082)

Currently:

* if a target release is set, we go ahead and clear the
remove-mupdate-override instruction from blueprints, regardless of
whether artifacts match
* if no target release is set, we don't do that

This behavior is inconsistent. We shouldn't gate the mupdate override
part of the state machine on a target release not being set.
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.

2 participants