-
Notifications
You must be signed in to change notification settings - Fork 401
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
multipath boot hangs with dracut-059 #2175
Comments
CC: @cthbleachbit, what was your reasoning behind your change, only the multipathd.service definition? did you try it? |
When I proposed that fix, the service defenition required the socket to present. Otherwise systemd would refused to enable the unit. I tried masking the socket unit again and this time systemd gives I'm not sure why including socket definition cause the service to hang in SUSE though. On my computer, multipathd did start normally in dracut environment. I should probably try to get suse in a VM and see what's going on |
Good, thanks for your feedback. I just wanted to know if this is a SUSE-only issue. |
This reverts commit e39ff40, removes an incorrect `Also=` directive from multipathd.service. `Also=multipathd.socket` is not the correct behavior for a socket-activated service. This directive has been removed upstream and dracut should do the same. This fixes #2289, #2175 where in the cleanup hook running multipath binary triggers activation of multipathd.service after it is stopped as dracut prepares to switch root in initrd-cleanup.service.
Fixed by #2290 |
This reverts commit e39ff40, removes an incorrect `Also=` directive from multipathd.service. `Also=multipathd.socket` is not the correct behavior for a socket-activated service. This directive has been removed upstream and dracut should do the same. This fixes dracutdevs#2289, dracutdevs#2175 where in the cleanup hook running multipath binary triggers activation of multipathd.service after it is stopped as dracut prepares to switch root in initrd-cleanup.service. (cherry picked from commit 297525c)
This reverts commit e39ff40, removes an incorrect `Also=` directive from multipathd.service. `Also=multipathd.socket` is not the correct behavior for a socket-activated service. This directive has been removed upstream and dracut should do the same. This fixes dracutdevs#2289, dracutdevs#2175 where in the cleanup hook running multipath binary triggers activation of multipathd.service after it is stopped as dracut prepares to switch root in initrd-cleanup.service.
Fixes boot hangs on s390x/multipath. - dracutdevs/dracut#2175 - dracutdevs/dracut#2289 - dracutdevs/dracut#2318
Fixes boot hangs on s390x/multipath. - dracutdevs/dracut#2175 - dracutdevs/dracut#2289 - dracutdevs/dracut#2318
Fixes boot hangs on s390x/multipath. - dracutdevs/dracut#2175 - dracutdevs/dracut#2289 - dracutdevs/dracut#2318
Describe the bug
Multipath is broken due to 02e646f
Distribution used
openSUSE Tumbleweed
Dracut version
059-358-g8ecd6e83
Init system
systemd 252.4
To Reproduce
Additional context
After creating an initrd without including
multipathd.socket
, the system boots.The definition of
multipathd.service
does not suggest that the inclusion is wrong:dracut/modules.d/90multipath/multipathd.service
Line 7 in 3c16c76
dracut/modules.d/90multipath/multipathd.service
Line 28 in 3c16c76
I'm not sure if this only affects openSUSE Tumbleweed, or if others are affected as well.
Edit: 02e646f reverted in 059+suse.360.g2e0ed5f7, so multipath works again in openSUSE Tumbleweed.
The text was updated successfully, but these errors were encountered: