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:
When launched inside chroot, "systemctl is-enabled" returns 0 when it fails to find requested unit. If launch in a real system (not in chroot), it returns 1. In RHEL 7.2 it always returned 1 and this seemed to be correct behavior.
Version-Release number of selected component (if applicable):
systemd-219-30
How reproducible:
Always
Steps to Reproduce:
1. Install RHEL 7.3
2. Boot from some LiveCD, mount RHEL 7.3 root, bind mount /proc inside it and chroot into it
3. Launch "systemctl is-enabled foo.bar" (provide it with any non-existing unit name)
Actual results:
systemctl prints "no such file or directory" but returns 0.
Expected results:
systemctl exits with non-zero status.
Additional info:
Setting "SYSTEMD_IGNORE_CHROOT" variable makes systemctl return 1, but this seems to be an ugly workaround, not a real solution.
This behavior is likely caused by "0296-install-follow-unit-file-symlinks-in-usr-but-not-etc.patch" and goes away if I disable this patch (together with several others which fails to apply without it). Can't point to particular reason, that patch introduces quite a few changes.