You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a first step toward improving things for coreos/fedora-coreos-tracker#1732, we should audit our docs (and Butane's & Ignition's ones) to make sure that we explicitly note that disk devices names may not be stable across boots.
Partitioning using Ignition and mount points should thus use labels as much as possible to reference to disk partitions to make sure they are stable across boots.
Ideally we should provide examples to update existing setups / mount units.
As a first step toward improving things for coreos/fedora-coreos-tracker#1732, we should audit our docs (and Butane's & Ignition's ones) to make sure that we explicitly note that disk devices names may not be stable across boots.
Partitioning using Ignition and mount points should thus use labels as much as possible to reference to disk partitions to make sure they are stable across boots.
Ideally we should provide examples to update existing setups / mount units.
See: https://github.com/openshift/os/blob/master/docs/faq.md#q-how-do-i-configure-a-secondary-block-device-via-ignitionmc-if-the-name-varies-on-each-node
--
As a second step, we need to mention using truly stable names for disks in Ignition config and the corresponding downsides that we have for now.
See: coreos/fedora-coreos-tracker#1732
The text was updated successfully, but these errors were encountered: