8000 fix(multipath): disable user_friendly_names with mpathconf by bmarzins · Pull Request #1306 · dracut-ng/dracut-ng · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix(multipath): disable user_friendly_names with mpathconf #1306

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

Merged
merged 1 commit into from
Apr 30, 2025

Conversation

bmarzins
Copy link
Contributor
@bmarzins bmarzins commented Apr 28, 2025

If dracut is creating /etc/multipath.conf by calling mpathconf in either multipathd-configure.service or multipathd.sh, there is a chance that the multipath config in the real root differs. Specifically, it might have chosen different user_friendly_names for the devices. When the systems switches to the real root, multipath may not be able to switch the devices to their configured names because those might already be in use. To avoid this, call mpathconf with "--user_friendly_names n" to create a multipath.conf with user_friendly_names disabled. If all devices use WWID names, it is always possible for multipath to rename them later.

Fixes b8a92b7 ("multipath: add automatic configuration for multipath")

This pull request changes...

Changes

Checklist

  • I have tested it locally
  • I have reviewed and updated any documentation if relevant
  • I am providing new code and test(s) for it

Fixes #
CC: @pvalena @jlebon

If dracut is creating /etc/multipath.conf by calling mpathconf in either
multipathd-configure.service or multipathd.sh, there is a chance that
the multipath config in the real root differs. Specifically, it might
have chosen different user_friendly_names for the devices. When the
systems switches to the real root, multipath may not be able to switch
the devices to their configured names because those might already be
in use. To avoid this, call mpathconf with "--user_friendly_names n"
to create a multipath.conf with user_friendly_names disabled. If all
devices use WWID names, it is always possible for multipath to rename
them later.

Fixes b8a92b7 ("multipath: add automatic configuration for multipath")
@bmarzins bmarzins requested a review from a team as a code owner April 28, 2025 21:56
@github-actions github-actions bot added modules Issue tracker for all modules multipath Issues related to the multipath module labels Apr 28, 2025
@jozzsi
Copy link
Contributor
jozzsi commented Apr 29, 2025

CC @mwilck

@mwilck
Copy link
Contributor
mwilck commented Apr 29, 2025

Ack, or rather non-nack, from my side. mpathconf is RH/Fedora specific, and this PR only touches the mpathconf code path.

@pvalena
Copy link
Contributor
pvalena commented Apr 29, 2025

LGTM, thanks!

@jlebon
Copy link
Contributor
jlebon commented Apr 30, 2025

Thanks, overall ack from me, though we'll get this tested on RHCOS and FCOS to be sure.

@Conan-Kudo Conan-Kudo enabled auto-merge (rebase) April 30, 2025 15:58
@Conan-Kudo Conan-Kudo merged commit 1d7464c into dracut-ng:main Apr 30, 2025
103 checks passed
jcapiitao added a commit to jcapiitao/fedora-coreos-config that referenced this pull request May 16, 2025
We are awaiting some dracut patches to land in Fedora mirror for [1].
We could wait for it, but we'd need it also for older rhcos branches
and those branches won't have the new dracut. So we decided to
carry part of the dracut-ng patch [2] in a post-script.
This will be backported in older rhcos branches, and will be reverted
on testing-devel once new dracut 107 available in mirror.

[1] coreos/fedora-coreos-tracker#1937
[2] dracut-ng/dracut-ng#1306
jcapiitao added a commit to jcapiitao/fedora-coreos-config that referenced this pull request May 19, 2025
We are awaiting some dracut patches to land in Fedora mirror for [1].
We could wait for it, but we'd need it also for older rhcos branches
and those branches won't have the new dracut. So we decided to
carry part of the dracut-ng patch [2] in a post-script.
This will be backported in older rhcos branches, and will be reverted
on testing-devel once new dracut 107 available in mirror.

[1] coreos/fedora-coreos-tracker#1937
[2] dracut-ng/dracut-ng#1306
jcapiitao added a commit to jcapiitao/fedora-coreos-config that referenced this pull request May 20, 2025
We are awaiting some dracut patches to land in Fedora mirror for [1].
We could wait for it, but we'd need it also for older rhcos branches
and those branches won't have the new dracut. So we decided to
carry part of the dracut-ng patch [2] in a post-script.
This will be backported in older rhcos branches, and will be reverted
on testing-devel once new dracut 107 available in mirror.

[1] coreos/fedora-coreos-tracker#1937
[2] dracut-ng/dracut-ng#1306
jcapiitao added a commit to jcapiitao/fedora-coreos-config that referenced this pull request May 20, 2025
We are awaiting some dracut patches to land in Fedora mirror for [1].
We could wait for it, but we'd need it also for older rhcos branches
and those branches won't have the new dracut. So we decided to
carry part of the dracut-ng patch [2] in a post-script.
This will be backported in older rhcos branches, and will be reverted
on testing-devel once new dracut 107 available in mirror.

[1] coreos/fedora-coreos-tracker#1937
[2] dracut-ng/dracut-ng#1306
jcapiitao added a commit to jcapiitao/fedora-coreos-config that referenced this pull request May 21, 2025
This test can be re-enable as we are applying part of the dracut-ng
patch [1] in a postprocess script. This script is a workaround
solution while awaiting the bump of dracut RPM NVR including [1] in
Fedora, and will be removed afterward.

[1] dracut-ng/dracut-ng#1306
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
modules Issue tracker for all modules multipath Issues related to the multipath module
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants
0