-
Notifications
You must be signed in to change notification settings - Fork 111
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
docs/faq: add question about unpredictable block device names #1382
Conversation
I guess it's probably worth linking to openshift/machine-config-operator#1720 in there. |
f61ff71
to
f0237c5
Compare
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.
Offhand looks like sane raw material that we can hopefully add to the official docs at some point.
## Q: How do I configure a secondary block device via Ignition/MC if the name varies on each node? | ||
|
||
First, verify that there isn't a `/dev/disk/by-*` symlink which works for your needs. If not, a few approaches exist: | ||
- If this is a fresh install and you're using the live environment to install RHCOS, as part of the install flow you can inspect the machine (by hand, or scripted) to imperatively figure out what the block device should be according to your own heuristics (e.g. "the only multipath device there is", or "the only NVMe block device"). You can then e.g. "render" the final Ignition config with the device path to pass to `coreos-installer` or directly partition it and optionally format it and use a consistent partition (and optionally filesystem) label that will be available to use in the generic Ignition config. |
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.
I'm pretty sure Assisted Installer ships some logic to do this.
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.
Do you have a link offhand? Definitely makes sense to link to AI docs if that's what the reader is actually using.
This has come up multiple times now.
f0237c5
to
1a68ae4
Compare
I think this one just needs a |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cgwalters, jlebon, travier The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This has come up multiple times now.