In this plot svg, remote-fs.target says that it runs After
iscsi.service, and network-online.target says that it runs before
iscsi.service, but the iscsi.service unit is disabled, so it doesn't
show up anywhere in the plot, except as a dependency of other units.
https://gordonmessmer.fedorapeople.org/systemd-plot/bootup-fedora-ws.svg
If I delete the unit entirely, then gdm.service runs before
network-online, which we want.
https://gordonmessmer.fedorapeople.org/systemd-plot/bootup-fedora-ws-no-iscsi.svg
So, the (apparent) bug is that iscsi.service is creating an ordering
dependency even though it's disabled.
This problem may be more difficult to diagnose because I can only
reproduce this problem on *some* systems, and I cannot find anything
they have in common. I don't know why it affects some systems and not
others.
I can reproduce the problem on my personal Fedora Workstation 42 install
(systemd-257.10-1.fc42.x86_64), but not the Workstation 43 install on my
employer-provided laptop.
I can reproduce the problem on a VM that boots the
Fedora-Workstation-43-Live ISO, but then it won't happen on the same VM
if I install Fedora on a virtual disk and boot from that disk instead of
the ISO.
The problem was brought to my attention by a user with Fedora 43 KDE.
How might I determine why systemd is starting remote-fs.target after
network-online.target on some systems, but not others, when all of them
have an iscsi.service unit which is disabled, and deleting that unit
appears to resolve the problem on the affected hosts?
