Thank you for the followup, Lars.
Based on your comment (and if I understood it correctly), the issue was
caused because of a local configuration choice instead of a bug in the
package itself. Therefore, I'm closing this bug as Invalid. Feel free
to reopen it and provide more details if you
After thinking a while about this, and having a look at our configuration for
focal I thik the reason for this issue during the upgrade is that the
`multipathd.service` and `multipathd.socket` were already masked in our focal
setup.
The `multipath-tools` packet is nevertheless attempting to
Hello and thanks for this bug report. I tried doing a `do-release-
upgrade -d` from Focal to Jammy, checking that multipathd was healthy in
the first place, before beginning the upgrade. I couldn't reproduce the
issue.
We're willing to investigate this failure case, but what we need are
some
Afterwards the unit is masked:
```
root@resolver-test:~# systemctl status multipath-tools
○ multipathd.service
Loaded: masked (Reason: Unit multipathd.service is masked.)
Active: inactive (dead)
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
The interessting part of the Error message is:
```
Failed to restart multipath-tools.service: Unit multipath-tools.service failed
to load properly, please adjust/correct and reload service manager: File exists
See system logs and 'systemctl status multipath-tools.service' for details.
