Bug 2154732
| Summary: | sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Frank Liang <xiliang> | ||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||
| Status: | CLOSED MIGRATED | QA Contact: | qe-baseos-daemons | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9.2 | CC: | dtardon, jnovy, libhe, linl, qzhang, systemd-maint-list, tumeya, vkuznets, xiaofwan, ymao, yoguo | ||||
| Target Milestone: | rc | Keywords: | Improvement, MigratedToJIRA, Triaged | ||||
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
||||
| Hardware: | aarch64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-09-20 23:13:33 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: |
|
||||||
(In reply to Frank Liang from comment #0) > Found this new fail in RHEL-9.2 testing, sys-fs-fuse-connections.mount does > exist and should not report this failure. The unit exists on the system, but the message comes from initrd... Btw, are you complaining just on a general principle, or does this actually cause problems? I doubt it very much this mount is needed in the initrd. But if anyone wants to send a patch upstream, be my guest... (In reply to David Tardon from comment #2) > Btw, are you complaining just on a general principle, or does this actually > cause problems? I doubt it very much this mount is needed in the initrd. But > if anyone wants to send a patch upstream, be my guest... This does not cause any problem so far and the message seems harmless too. Just wondering why it appears in RHEL-9.2 testing and not in RHEL-9.1. What's the difference that trigger this log? If it is expected, we can ignore it safely in our testing.Thanks (In reply to Frank Liang from comment #3) > This does not cause any problem so far and the message seems harmless too. > Just wondering why it appears in RHEL-9.2 testing and not in RHEL-9.1. > What's the difference that trigger this log? No idea. I don't see it locally. Are there any obvious differences between the new initrd and an old one where this didn't show, e.g., something in the new initrd that actually uses FUSE? (Just use `lsinitrd` to list the content of both initrds and then `diff -u` to compare them.) I found the same issue on x86_64 since compose RHEL-9.2.0-20230127.12. After upgraded to RHEL-9.2.0-20230206.16, not see the failure message. Compared with previous version, it does not have fuse-overlayfs.conf in initrd. Is it the reason? And I am not clear which component brought it into initrd before. # lsinitrd initramfs-5.14.0-252.el9.aarch64.img|grep -i fuse drwxr-xr-x 2 root root 0 Dec 14 15:20 usr/lib/modules/5.14.0-252.el9.aarch64/kernel/fs/fuse -rw-r--r-- 1 root root 78568 Dec 14 15:20 usr/lib/modules/5.14.0-252.el9.aarch64/kernel/fs/fuse/fuse.ko.xz -rw-r--r-- 1 root root 18044 Dec 14 15:20 usr/lib/modules/5.14.0-252.el9.aarch64/kernel/fs/fuse/virtiofs.ko.xz Below is from RHEL-9.2.0-20230127.12. # lsinitrd initramfs-5.14.0-244.el9.aarch64.img|grep -i fuse drwxr-xr-x 2 root root 0 Dec 14 15:20 usr/lib/modules/5.14.0-244.el9.aarch64/kernel/fs/fuse -rw-r--r-- 1 root root 77660 Dec 14 15:20 usr/lib/modules/5.14.0-244.el9.aarch64/kernel/fs/fuse/fuse.ko.xz -rw-r--r-- 1 root root 17784 Dec 14 15:20 usr/lib/modules/5.14.0-244.el9.aarch64/kernel/fs/fuse/virtiofs.ko.xz -rw-r--r-- 1 root root 5 Dec 8 15:20 usr/lib/modules-load.d/fuse-overlayfs.conf # cat /usr/lib/modules-load.d/fuse-overlayfs.conf fuse This failure can be seen on AliCloud with the released RHEL9.2 image.
[root@iZbp11s3197xqpx25ir8grZ ~]# virt-what
alibaba_cloud
kvm
[root@iZbp11s3197xqpx25ir8grZ ~]# uname -r
5.14.0-284.11.1.el9_2.x86_64
[root@iZbp11s3197xqpx25ir8grZ ~]# systemctl status sys-module-fuse.device
● sys-module-fuse.device - /sys/module/fuse
Loaded: loaded
Active: active (plugged) since Fri 2023-05-19 18:25:38 CST; 7h left
Until: Fri 2023-05-19 18:25:38 CST; 7h left
Device: /sys/module/fuse
May 19 18:25:36 localhost systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found.
[root@iZbp11s3197xqpx25ir8grZ ~]# lsinitrd /boot/initramfs-5.14.0-284.11.1.el9_2.x86_64.img | grep -i fuse
-rw-r--r-- 1 root root 5 Feb 15 00:45 usr/lib/modules-load.d/fuse-overlayfs.conf
drwxr-xr-x 2 root root 0 Feb 15 00:45 usr/lib/modules/5.14.0-284.11.1.el9_2.x86_64/kernel/fs/fuse
-rw-r--r-- 1 root root 87164 Feb 15 00:45 usr/lib/modules/5.14.0-284.11.1.el9_2.x86_64/kernel/fs/fuse/fuse.ko.xz
-rw-r--r-- 1 root root 19644 Feb 15 00:45 usr/lib/modules/5.14.0-284.11.1.el9_2.x86_64/kernel/fs/fuse/virtiofs.ko.xz
[root@iZbp11s3197xqpx25ir8grZ ~]# cat /usr/lib/modules-load.d/fuse-overlayfs.conf
fuse
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |
Created attachment 1933519 [details] os_tests.tests.test_general_check.TestGeneralCheck.test_check_journalctl_fail.debug Description of problem: Found this new fail in RHEL-9.2 testing, sys-fs-fuse-connections.mount does exist and should not report this failure. # systemctl status sys-module-fuse.device ● sys-module-fuse.device - /sys/module/fuse Loaded: loaded Active: active (plugged) since Mon 2022-12-19 02:35:05 UTC; 3min 50s ago Until: Mon 2022-12-19 02:35:05 UTC; 3min 50s ago Device: /sys/module/fuse Dec 19 02:35:02 localhost systemd[1]: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found. # rpm -ql systemd|grep sys-fs-fuse-connections.mount /usr/lib/systemd/system/sys-fs-fuse-connections.mount /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount # ls -l /usr/lib/systemd/system/sys-fs-fuse-connections.mount -rw-r--r--. 1 root root 1146 Oct 31 18:59 /usr/lib/systemd/system/sys-fs-fuse-connections.mount # ls -l /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount lrwxrwxrwx. 1 root root 32 Dec 9 09:29 /usr/lib/systemd/system/sysinit.target.wants/sys-fs-fuse-connections.mount -> ../sys-fs-fuse-connections.mount # rpm -q systemd systemd-252-2.el9.aarch64 RHEL Version: RHEL-9.2(5.14.0-212.el9.aarch64) How reproducible: 100% Steps to Reproduce: 1. Create an RHEL-9.2 instance 2. Check journal log after boot up Actual results: Unit sys-fs-fuse-connections.mount not found while it exists Expected results: No such fail log Additional info: - N/A