Skip to content

Conversation

jgallagher
Copy link
Contributor

... unless a mupdate has occurred, in which case we allow it.

Fixes #8056.

…ogress

... unless a mupdate has occurred, in which case we allow it.

Fixes #8056.
@jgallagher
Copy link
Contributor Author

This definitely needs some testing on a racklette before merging, but I believe implements what we decided to do for R17.

Comment on lines +292 to +294
// Convert this to a string; comparing "system version as a string" to
// "artifact version as a string" below feels bad, but is maybe fine? The
// artifact versions are loaded from the DB by joining
Copy link
Contributor

Choose a reason for hiding this comment

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

It seems like this part of the comment should be above let current_target_version = current_target_version.to_string(); and there should be additional text after "... from the DB by joining"?

&bp,
&current_target_version
));
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think you need a logctx.cleanup_successful(); at the end of this test

Comment on lines +393 to +394
// * We don't keep the desired state of all Hubris components in the
// blueprint anyway.
Copy link
Contributor

Choose a reason for hiding this comment

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

Not for this PR, but is this something we should have? It feels a little dangerous to not have any kind of ongoing update check for the Hubris components. WDYT?

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.

Restrict changes to target_release during an update

2 participants