-
Notifications
You must be signed in to change notification settings - Fork 62
[omdb] Add RoT bootloader, RoT, and host OS information to omdb nexus update-status
#8901
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Testing this on a racklette looks good: Before uploading a TUF repo: After uploading the TUF repo I used to set up the racklette and setting it as the target release, we know all the hubris and host OS versions: Enabling the planner made one blueprint, which did the noop zone conversion, so now we know all the zone versions too: After manually downgrading all the Hubris images (we still know the versions in the inactive RoT and SP slots, but no longer no the versions of the bootloader or the active RoT / SP slots): After uploading a newer TUF repo, the versions for the inactive Hubris images changed, because those images were the same in both TUF repos. The host OS and zone versions did not change, because those artifacts were different in the two repos: After the update completed, all the host OS entries and zones are on the new version, and we see the old version in the inactive slot of the host OS: |
andrewjstone
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great.
I'll give this a spin on a racklette and report back before merging, but I think this is straightforward enough to go ahead and review without that.
Closes #8883.