Bug 1943263
| Summary: | Only lo network interface starts | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Ulrich Drepper <drepper> | ||||||||||
| Component: | systemd | Assignee: | systemd-maint | ||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 33 | CC: | fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | systemd-246.14-1.fc33 | Doc Type: | If docs needed, set a value | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2021-05-27 01:04:22 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Ulrich Drepper
2021-03-25 16:58:01 UTC
Is this using systemd-networkd or NetworkManager to configure the network? Please at least paste 'ip a' and 'networkctl status "*"'. Full logs from the boot would be useful too. Created attachment 1766560 [details]
ip a after booting
Created attachment 1766562 [details]
ip a after systemd-networkd restart
After I ran 'systemctl restart systemd-networkd' from the console
Created attachment 1766563 [details]
networkctl output after booting
Created attachment 1766564 [details]
networkctl output after networkd restart
after the manual systemd-networkd restart
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) > Is this using systemd-networkd or NetworkManager to configure the network? > > Please at least paste 'ip a' and 'networkctl status "*"'. Full logs from the > boot > would be useful too. I provided the output of the commands. It complains about DHCP but that service does work, I can immediately after the bootup reliably restart networkd. Oh, OK. So systemd-networkd is not running, most likely because it is not enabled. I guess we screwed up the scriptlet to set enablement when the package was split out. (In reply to Zbigniew Jędrzejewski-Szmek from comment #7) > Oh, OK. So systemd-networkd is not running, most likely because it is not > enabled. I guess we screwed > up the scriptlet to set enablement when the package was split out. You're right, that's all that it is. After I explicitly enable systemd-networkd it now works. This should really be fixed, seems like a bad bug. BTW, this is the server edition of Fedora, in case it makes a difference. I updated my desktop machine back when from earlier Fedora versions to 33 and cannot recall any problem like that. The desktop uses the desktop edition. (In reply to Ulrich Drepper from comment #8) > This should really be fixed, seems like a bad bug. I determined I had the same problem on another machine. There, though, the IPv4 address was for some reason configured but not the IPv6 address. The result were long connection times until the IPv6 connection timed out. (In reply to Ulrich Drepper from comment #9) > I determined I had the same problem on another machine. There, though, the > IPv4 address was for some reason configured but not the IPv6 address. The > result were long connection times until the IPv6 connection timed out. To give people more chances to discover this solution: on yet another machine the network interfaces came up (IPv4 and IPv6) but systemd-resolved never remembered the non-standard settings it can derive from the DHCP requests. I added special rules and only after enable systemd-networkd are they now remembered over a restart. FEDORA-2021-8595b30af3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 FEDORA-2021-8595b30af3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8595b30af3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8595b30af3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-8595b30af3 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-25202922d4 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-25202922d4 FEDORA-2021-25202922d4 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-25202922d4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-25202922d4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-25202922d4 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |