stable

systemd-249.12-5.fc35

FEDORA-2022-6d2c62d6d6 created by adamwill 2 years ago for Fedora 35

This update is intended to resolve a bug that prevents network installations from original Fedora 35 install media from working with the current updated systemd package. It should not have any effect on already installed systems. Fresh network installs should work (not crash) and result in the installed system's /etc/resolv.conf being a symlink to systemd-resolved's dynamic stub file (/run/systemd/resolve/stub-resolv.conf).

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2022-6d2c62d6d6

This update has been submitted for testing by adamwill.

2 years ago

This update's test gating status has been changed to 'waiting'.

2 years ago

This update's test gating status has been changed to 'failed'.

2 years ago

This update has been pushed to testing.

2 years ago
User Icon imsedgar commented & provided feedback 2 years ago
karma

Does not solve the installation problem.

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'

This update's test gating status has been changed to 'passed'.

a year ago
User Icon adamwill commented & provided feedback a year ago

@imsedgar I don't think that's quite accurate. It does solve the crash, and will work as expected for I think most installs. You only found a fairly specific case where it doesn't behave as intended. It still seems a lot better than the current situation (all netinsts crash), unless I'm missing something.

User Icon imsedgar commented & provided feedback a year ago
karma

@adamwill Ok, your are right. It solves the crash. It is better than current systemd-249.12-3.fc35.

But the dns search path is "." now, so only fully qualified names can be resolved. Hopefully we can also solve this too in another update?

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
User Icon adamwill commented & provided feedback a year ago

yeah, to be fair, I didn't quite understand the problem properly at first. I thought it was more restricted than it is. You're saying that any time the DHCP server provides a search domain that doesn't wind up in /etc/resolv.conf on the installed system, right?

User Icon imsedgar commented & provided feedback a year ago

Yes. The search domain provided by the DHCP server is stored in /etc/resolv.conf on the runtime installation system, and it is copied to the installed system when using the original released Fedora 35 system. The search path is also copied as value of attribute dns-search in section ipv4 of /etc/NetworkManager/system-connections/.nmconnection of the connection that is active during installation. This provides the value which is used by systemd-resolved after reboot even if /etc/resolv.conf is a symbolic link to the stub file. But with systemd-249.12-4.fc35 the dns search domain info is lost on the installed system, the file .nmconnection only contains "dns-search=".

User Icon imsedgar commented & provided feedback a year ago

The unusable /etc/resolv.conf (because it is a symlink and systemd-resolved isn't running) also affects %post section in my kickstart file. Originally I count mount a nfs partition (read-only, full qualified domain name) which I need to copy some files to the installed system that are used after reboot. Now, with systemd-249.12-4.fc35, I found in the log (of %post): mount.nfs: Resource temporarily unavailable

This is the reason why my own postinstallation scripts after the first reboot doesn't run (because they wasn't installed during %post). It could be that the kickstart file can modify itself to contain more data instead of fetching files from the file system (as a workaround).

User Icon imsedgar commented & provided feedback a year ago

Oh, I just need to mention that I configure kickstart to create a static network configuration for our workstations and servers, because these should not depend on a running DHCP server. The DHCP server is running for notebooks and for (all) system installation with PXE.

I havn't tested it, but all systems that uses (only) dynamic network configuration are not affected by the dns search domain problem, because they will receive actual data at each boot (more precisely: every time a network connection is started).

So, our configuration may be a special case?

adamwill edited this update.

New build(s):

  • systemd-249.12-5.fc35

Removed build(s):

  • systemd-249.12-4.fc35

Karma has been reset.

a year ago

This update has been submitted for testing by adamwill.

a year ago

This update has been pushed to testing.

a year ago
User Icon imsedgar commented & provided feedback a year ago
karma

systemd-249.12-5.fc35 solves the problem that dns resolution didn't work in kickstart %post section.

My kickstart %post section can mount a nfs partion. DNS resolution also works after reboot.

DNS search domain isn't preserved, but it doesn't matter for me now, because now my scripts run again and they set the dns search domain if it does not match the value from our preset list.

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
User Icon adelton provided feedback a year ago
karma
BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'

This update can be pushed to stable now if the maintainer wishes

a year ago

This update has been submitted for stable by adamwill.

a year ago

This update has been pushed to stable.

a year ago

Please login to add feedback.

Metadata
Type
bugfix
Severity
urgent
Karma
2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
2 years ago
in testing
a year ago
in stable
a year ago
modified
a year ago
BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
0
2

Automated Test Results

Test Cases

0 0 Test Case base service manipulation
0 0 Test Case base services start
0 0 Test Case base shutdown/reboot