sts-sponsors team mailing list archive
-
sts-sponsors team
-
Mailing list archive
-
Message #00699
[Bug 1673255] [NEW] drbd udev rule with multiple symlinks fails
You have been subscribed to a public bug by Dan Streetman (ddstreet):
The drbd udev rule creates multiple symlinks with a single udev rule, by space-separating them inside an env var. However, recent udev changes no longer allow doing that:
https://github.com/systemd/systemd/issues/4833
Now, recent versions of udev will, by default, replace any whitespace
introduced into SYMLINK values by variable substitution, so the drbd
udev rule that does this breaks:
ENV{SYMLINK}!="", SYMLINK="$env{SYMLINK}", GOTO="have_symlink"
when that SYMLINK env variable contains multiple symlinks, they are
combined into a single symlink with an underscore joining them.
Instead, since it's desired to leave all spaces in the env var in order
to create multiple symlinks, the rule needs to use the
"string_escape=none" option which prevents whitespace replacement:
ENV{SYMLINK}!="", SYMLINK="$env{SYMLINK}",
OPTIONS+="string_escape=none", GOTO="have_symlink"
Related ubuntu bug that introduced the new udev default whitespace replacement behavior:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485
** Affects: drbd-utils (Ubuntu)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: drbd-utils (Ubuntu Trusty)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: Invalid
** Affects: drbd-utils (Ubuntu Xenial)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: drbd-utils (Ubuntu Artful)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: drbd-utils (Ubuntu Bionic)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: drbd-utils (Ubuntu Cosmic)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Affects: drbd-utils (Debian)
Importance: Unknown
Status: Unknown
--
drbd udev rule with multiple symlinks fails
https://bugs.launchpad.net/bugs/1673255
You received this bug notification because you are a member of STS Sponsors, which is subscribed to the bug report.