Public bug reported:
The multipathd daemon is not started in containers, as multipath-
tools.service sets:
ConditionVirtualization=!container
but this doesn't prevent it from running on VMs, including those started
by using cloud images. I don't think enabling multipathd in VMs makes
much sense, at least by default, especially given that we care about
boot speed. Setting
ConditionVirtualization=false
should prevent it from getting started on any virtualized environment.
The container-only exclusion was added because multipathd *fails* to
start in containers (see LP: #1823093).
** Affects: multipath-tools (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- multipathd started by default on VM instances
+ multipathd gets started by default on VM instances
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904920
Title:
multipathd gets started by default on VM instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1904920/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
