Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:
# systemctl enable qarshd.socket
Failed to issue method call: Unit qarshd.socket is not loaded.

If I start the service and then do enable, it works as expected.
Stopping and disabling the service will lead to the same scenario (enabling it again won't work without start)

Version-Release number of selected component (if applicable):
systemd-python-208-1.el7.x86_64
systemd-sysv-208-1.el7.x86_64
systemd-libs-208-1.el7.x86_64
systemd-208-1.el7.x86_64


How reproducible:
always

Steps to Reproduce:
1. enable service without prior starting it (ideally take some from systemctl list-unit-files)
2.
3.

Actual results:
Failed to issue method call: Unit <service> is not loaded.


Expected results:
service enabled

Additional info:
did not occur until 0212 snap.

For iscsi it cannot be enabled even thought it can be started.

+ echo -e 'iscsi.service: '
iscsi.service:
+ systemctl -q is-active iscsi.service
+ echo -ne '\tactivating... '
        activating... + systemctl start iscsi.service
+ systemctl -q is-enabled iscsi.service
+ echo -ne '\tenabling... '
        enabling... + systemctl enable iscsi.service
Failed to issue method call: Unit iscsi.service is not loaded.

This was broken by commit
commit 47cc7b870802f9fa1a205e62c8aa9d83b47f2be5
selinux: Check access vector for enable and disable perm for each unit file

after revert it works fine.

Created attachment 863283 [details]
Proper fix

*** Bug 1065408 has been marked as a duplicate of this bug. ***

*** Bug 1066855 has been marked as a duplicate of this bug. ***

Tested the -3 package and it fixed the problem for me.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.