Closed gursewak1997 closed 1 year ago
From the initial investigation, it looks like the changes in the latest fedora-release package activate the network-online.target
; resulting in the test failure.
Pinning to the previous fedora-release
package for now in rawhide.
So it's this transition that introduced the issue:
fedora-release-common 38-0.8 -> 38-0.15
fedora-release-coreos 38-0.8 -> 38-0.15
fedora-release-identity-coreos 38-0.8 -> 38-0.15
Seems like one of the commits in the last 7 days introduced some side effect here.
Looks like it's the enabling of podman-restart.service
because it has Wants=network-online.target
.
cc @jlebon on the recommended path forward here since he notably wrote the nice explanation in https://github.com/coreos/fedora-coreos-config/pull/1088
I think this usage of network-online.target
is not ideal, but OK. podman-restart.service
is a "leaf" service, so shouldn't be delaying boot in a way that significantly affects the UX (whereas the pinger service also had Before=systemd-user-sessions.service
). But still, it'd be nice to strengthen podman semantics so it could be avoided, so I added a comment in https://bugzilla.redhat.com/show_bug.cgi?id=2149642.
The commit has been reverted. Once we have a new rawhide build of fedora-release
, we should be able to revert https://github.com/coreos/fedora-coreos-config/pull/2172.
https://github.com/coreos/fedora-coreos-config/pull/2192 closes the loop on this.
Describe the bug
Kola test
ext.config.networking.network-online-service
fails afternetwork-online.target
activates beforehand. By default we no longer pull innetwork-online.target
and hence thenetwork-online.target
should be inactive.Rawhide Build console.txt From console.txt
Reproduction steps
systemctl show -p ActiveState network-online.target
. It will tell that thenetwork-online.target
is active.Expected behavior
Unit
network-online.target
remains inactiveActual behavior
System details
Ignition config
No response
Additional information
No response