Repository navigation
Make disk location required in sled-agent inventory and Nexus #11628
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
Draft
smklein
wants to merge
2
commits into
topo-disk-scan
Choose a base branch
from
required-disk-location
base: topo-disk-scan
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🟡 (optional) Right after an upgrade,
omdb nexus sleds expunge-diskcan skip its "disk is PRESENT" safety prompt for a disk that is still installed. Reading a collection now silently drops every disk row whoselocationis NULL. Every collection written before schema version 313 (inv-physical-disk-location) has NULL there. Fix: keep NULL-location disks visible to readers that only check presence, or have the omdb expunge check fall back toinv_physical_diskrows. Another option is to warn when the latest collection skipped disks.Why this was flagged
The trigger is an operator expunging a disk after the schema migration and before new Nexus finishes its first collection. In that window the latest collection was written by pre-313 Nexus, so
locationis NULL on everyinv_physical_diskrow. The read at inventory.rs:3488-3491 hitslet Some(location) = disk.location else { nskipped += 1; continue; }and returns sleds with emptydisks. dev-tools/omdb/src/bin/omdb/nexus.rs:5734-5740 then finds no match insleds_containing_disk. Its0 => {}arm skips the "WARNING: physical disk ... is PRESENT" prompt, so an installed disk is expunged without confirmation. On the base branch the row read back withlocation: Noneand the prompt fired. The only signal is a Nexus logwarn!, which omdb never sees. The window lasts until the first new collection;inventory.period_secs_collect = 600, but one also runs at startup.Verification: After schema 313, the latest collection can still have NULL
locationrows. The diff addslet Some(location) = disk.location else { nskipped += 1; continue; };ininventory_collection_read, so those disks never reachsled_agents[..].disks. In dev-tools/omdb/src/bin/omdb/nexus.rs:5720-5740,sleds_containing_disk.len()is 0, so the "PRESENT" y/N prompt at 5744-5753 never shows. On the base branch, the disk stayed visible.