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.
DescriptionLukas Slebodnik
2017-10-10 12:08:51 UTC
Description of problem:
The latest upgrade the package redhat-release broke many tests because it changed location of systemd preset files and therefore many daemons are not started after booting machine
Version-Release number of selected component (if applicable):
sh$ rpm -q redhat-release
redhat-release-7.5-0.7.el7.x86_64
How reproducible:
Deterministic
Steps to Reproduce:
1. rpm -ql redhat-release | grep "/usr/lib/systemd/system-preset"
Actual results:
sh$ rpm -ql redhat-release | grep "/usr/lib/systemd/system-preset"
sh$ echo $?
1
Expected results:
sh$ rpm -ql redhat-release | grep "/usr/lib/systemd/system-preset"
/usr/lib/systemd/system-preset
/usr/lib/systemd/system-preset/85-display-manager.preset
/usr/lib/systemd/system-preset/90-default.preset
Additional info:
https://www.freedesktop.org/software/systemd/man/systemd.preset.html
The following in kickstart's %post helps a bit:
if [[ -f /usr/lib64/systemd/system-preset/90-default.preset ]]; then
echo "Looks like we have an incorrect redhat-release '$(rpm -q redhat-release)'. Fixing..."
ln -s -t /usr/lib/systemd/system-preset/ /usr/lib64/systemd/system-preset/*
systemctl preset-all
fi
(In reply to Lubos Kocman from comment #8)
> I did exchange all of _libdir back to prefix/lib. Seems like fedora-release
> uses hardcoded /usr/lib anyway.
That is because there is no macro for /usr/lib. /usr part of the path can be replaced with %{_prefix} which makes possible to build rpms for systems that didn't do usr-move (not relevant for RHEL or Fedora).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0700