Hide Forgot
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.
*** This bug has been marked as a duplicate of bug 1413964 ***