FEDORA-2022-f38f479b8f created by zbyszek 4 months ago for Fedora 35
stable
  • Create /etc/resolv.conf symlink if nothing is present yet (#2032085)
  • Add missing requirements for libfido2 and libtss2 (#1975827)
  • Allow mprotect(2), arch_prctl(2) in @default seccomp filter, bpf(2) and /proc for systemd-udev (#2027627)
  • Various documentation fixes (#1926323)
  • Fix sysusers without /proc (#2036217)
  • Various fixes to condition handling (#1919538)
  • Bugfixes for the manager, systemd-networkd, systemd-journald and journalctl, systemd-analyze, systemd-resolved, systemd-homed, shell completions, systemd-detect-virt on MS Hyper-V, nss modules
  • Ordering of various units during early boot and shutdown is adjusted to fix some corner cases
  • Maximum numbers of files are bumped for /dev and /tmp
  • fstab-generator now ignores root-on-nfs/cifs/iscsi and live (#2037233)
  • CVE-2021-3997, #2024639: systemd-tmpfiles would exhaust the stack and crash during excessive recursion on a very deeply nested directory structure.
  • Some minor documentation fixes and a fix for journalctl
  • Make systemd-xdg-autostart-service ignore missing condition check binary (related to #2038750, but does not fix it)

No need to log out or reboot.

How to install

sudo dnf upgrade --advisory=FEDORA-2022-f38f479b8f

This update has been submitted for testing by zbyszek.

4 months ago

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

4 months ago

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

4 months ago

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

4 months ago

This update has been pushed to testing.

4 months ago
User Icon imabug provided feedback 4 months ago
karma
User Icon bojan commented & provided feedback 4 months ago
karma

Works.

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

4 months ago

zbyszek edited this update.

4 months ago

zbyszek edited this update.

4 months ago

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

4 months ago
User Icon thesourcehim commented & provided feedback 4 months ago
karma

System enters emergency mode on boot asking for root password. Pressing Ctrl+D allows to boot normally though.

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

4 months ago

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

4 months ago
User Icon zbyszek commented & provided feedback 4 months ago

@thesourcehim: please file a bug in bugzilla. It's hard to say what the problem is just from this one snippet.

User Icon clnetbox commented & provided feedback 4 months ago
karma

@zbyszek : I can confirm what @thesourcehim reported ... The system boots into emergency mode.
I checked the logs in emergency mode, but couldn't find something useful to report in a bug report.

Unfortunately I don't know what has been changed in the packages that causes this behavior.
For now I have reverted back to the stable version and everything works without issues again.

User Icon zbyszek commented & provided feedback 4 months ago

OK, can you at least paste the full logs from the failed boot somewhere?

User Icon clnetbox commented & provided feedback 4 months ago

@zbyszek : Unfortunately not ... I always remove the /var/log/journal directory after the system installation.
Maybe @thesourcehim makes use of journal archiving, and can give you the log details you are asking for ?

User Icon clnetbox commented & provided feedback 4 months ago

@zbyszek : In case it helps you ... These packages are currently installed.

systemd.x86_64                                    249.7-2.fc35
systemd-container.x86_64                          249.7-2.fc35
systemd-libs.x86_64                               249.7-2.fc35
systemd-networkd.x86_64                           249.7-2.fc35
systemd-oomd-defaults.noarch                      249.7-2.fc35
systemd-pam.x86_64                                249.7-2.fc35
systemd-resolved.x86_64                           249.7-2.fc35
systemd-rpm-macros.noarch                         249.7-2.fc35
systemd-udev.x86_64                               249.7-2.fc35  
User Icon nphilipp commented & provided feedback 4 months ago
karma

Confirming what @thesourcehim and @clnetbox experienced, I opened a bug: https://bugzilla.redhat.com/show_bug.cgi?id=2039888

This update has been unpushed.

zbyszek edited this update.

New build(s):

  • systemd-249.9-1.fc35

Removed build(s):

  • systemd-249.8-1.fc35

Karma has been reset.

4 months ago

This update has been submitted for testing by zbyszek.

4 months ago

zbyszek edited this update.

4 months ago

This update has been pushed to testing.

4 months ago
User Icon bojan commented & provided feedback 4 months ago
karma

Still boots here on 2 machines.

User Icon besser82 commented & provided feedback 4 months ago
karma

Works great! LGTM! =)

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

4 months ago
User Icon thesourcehim commented & provided feedback 4 months ago
karma

Works

User Icon clnetbox commented & provided feedback 4 months ago
karma

The system boots successfully without issues now. Thanks @zbyszek !

karma
User Icon atim provided feedback 4 months ago
karma
User Icon ibims commented & provided feedback 4 months ago

is it worth to push it to stable?

User Icon geraldosimiao commented & provided feedback 4 months ago
karma

with 249.9-1 all is fine

This update has been submitted for stable by zbyszek.

4 months ago

This update has been pushed to stable.

4 months ago
User Icon harrymichal commented & provided feedback 4 months ago
karma

The user-runtime-dir.service fails on Fedora Silverblue making Wayland unavailable and systemd --user unusable.

× user-runtime-dir@1000.service - User Runtime Directory /run/user/1000
     Loaded: loaded (/usr/lib/systemd/system/user-runtime-dir@.service; static)
     Active: failed (Result: exit-code) since Wed 2022-01-19 16:41:21 EET; 4min 32s ago
       Docs: man:user@.service(5)
    Process: 1540 ExecStart=/usr/lib/systemd/systemd-user-runtime-dir start 1000 (code=exited, status=1/FAILURE)
   Main PID: 1540 (code=exited, status=1/FAILURE)
        CPU: 18ms

tammi 19 16:41:21 marty-t460 systemd[1]: Starting User Runtime Directory /run/user/1000...
tammi 19 16:41:21 marty-t460 systemd-user-runtime-dir[1540]: mmap: Permission denied
tammi 19 16:41:21 marty-t460 systemd-user-runtime-dir[1540]: Failed to mount per-user tmpfs directory /run/user/1000: No such file or directory
tammi 19 16:41:21 marty-t460 systemd[1]: user-runtime-dir@1000.service: Main process exited, code=exited, status=1/FAILURE
tammi 19 16:41:21 marty-t460 systemd[1]: user-runtime-dir@1000.service: Failed with result 'exit-code'.
tammi 19 16:41:21 marty-t460 systemd[1]: Failed to start User Runtime Directory /run/user/1000.
User Icon zbyszek commented & provided feedback 4 months ago

@harrymichal: this update has gone stable a few days ago, so commenting here is not going to be effective. Open a bug instead. This looks like a selinux issue, please include avc logs and information about versions of systemd and selinux policy.

User Icon clnetbox commented & provided feedback 4 months ago

@harrymichal There is a lot of trouble with the two latest selinux-policy releases 35.9 and 35.10 ...
You may want to check out https://bodhi.fedoraproject.org/updates/FEDORA-2022-41fa7610dd.
If you have installed one of them, downgrade to version 35.8, and check if the problem still occurs.


Please login to add feedback.

Metadata
Type
security
Severity
high
Karma
7
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 months ago
in testing
4 months ago
in stable
4 months ago
modified
4 months ago
BZ#1926323 Wrong default for DNSSEC in resolved.conf (in man page)
0
0
BZ#1975827 Additional requirements for LUKS2 + pkcs11
0
0
BZ#2022816 Symbolic link for /etc/resolv.conf is not created during kickstart Fedora 35
0
0
BZ#2027627 systemd-udevd syscall filtering blocks access to bpf() syscall
0
0
BZ#2032085 Some variants are missing /etc/resolv.conf symlink (use systemd-resolved)
0
0
BZ#2036217 Bare metal install @"minimal install" gives "Failed to change ownership .. : function not implemented"
0
0
BZ#2037233 generated sysroot.mount in nfsroot case (initramfs) is wrong
0
0
BZ#2039383 CVE-2021-3997 systemd: Uncontrolled recursion in systemd-tmpfiles when removing files [fedora-all]
0
0

Automated Test Results

Test Cases

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