2154732 – sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found

This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2154732 - sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found

Summary: sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit ...

Keywords:
Status:	CLOSED MIGRATED
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	dracut
Sub Component:
Version:	9.2
Hardware:	aarch64
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	dracut-maint-list
QA Contact:	qe-baseos-daemons
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2022-12-19 03:01 UTC by Frank Liang
Modified:	2023-10-25 06:00 UTC (History)
CC List:	11 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2023-09-20 23:13:33 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
os_tests.tests.test_general_check.TestGeneralCheck.test_check_journalctl_fail.debug (254.86 KB, text/plain) 2022-12-19 03:01 UTC, Frank Liang	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHEL-5714	0	None	Migrated	None	2023-09-20 23:13:28 UTC
Red Hat Issue Tracker	RHELPLAN-142846	0	None	None	None	2023-05-19 02:51:01 UTC

Description Frank Liang 2022-12-19 03:01:56 UTC

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

Comment 1 David Tardon 2023-01-06 14:00:56 UTC

(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...

Comment 2 David Tardon 2023-01-11 14:23:58 UTC

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...

Comment 3 Frank Liang 2023-01-11 14:46:34 UTC

(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

Comment 4 David Tardon 2023-01-12 10:07:29 UTC

(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.)

Comment 5 Xiaofeng Wang 2023-01-30 10:14:21 UTC

I found the same issue on x86_64 since compose RHEL-9.2.0-20230127.12.

Comment 6 Frank Liang 2023-02-06 13:55:17 UTC

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

Comment 7 YongkuiGuo 2023-05-19 02:49:57 UTC

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

Comment 8 RHEL Program Management 2023-09-20 23:12:30 UTC

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.

Comment 9 RHEL Program Management 2023-09-20 23:13:33 UTC

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.

Note You need to log in before you can comment on or make changes to this bug.