Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1500336 - redhat-release-7.5-0.7 ships systemd preset file in wrong directory
redhat-release-7.5-0.7 ships systemd preset file in wrong directory
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: redhat-release (Show other bugs)
7.5
All Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Lubos Kocman
Release Test Team
: Regression
: 1500839 1500850 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-10-10 08:08 EDT by Lukas Slebodnik
Modified: 2018-04-10 06:18 EDT (History)
12 users (show)

See Also:
Fixed In Version: redhat-release-7.5-0.8.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1506384 (view as bug list)
Environment:
Last Closed: 2018-04-10 06:17:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:0700 None None None 2018-04-10 06:18 EDT

  None (edit)
Description Lukas Slebodnik 2017-10-10 08:08:51 EDT
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
Comment 3 Marian Csontos 2017-10-12 03:33:49 EDT
*** Bug 1500839 has been marked as a duplicate of this bug. ***
Comment 4 Marian Csontos 2017-10-12 03:40:25 EDT
...and sshd is not started among others so this breaks access to machine (unless one has remote console.)
Comment 5 Lukáš Nykrýn 2017-10-12 03:52:18 EDT
THis was caused by:
http://pkgs.devel.redhat.com/cgit/rpms/redhat-release/commit/?h=rhel-7.5&id=0dff430977d4da1215246d88b4732e1d84e35d90

/usr/lib/ should be replaced with %{_prefix}/lib and not by %{_libdir}
Comment 6 Martin Cermak 2017-10-12 04:07:15 EDT
*** Bug 1500850 has been marked as a duplicate of this bug. ***
Comment 7 Marian Csontos 2017-10-12 04:08:11 EDT
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
Comment 8 Lubos Kocman 2017-10-13 02:05:52 EDT
I did exchange all of  _libdir back to prefix/lib. Seems like fedora-release uses hardcoded /usr/lib anyway.

Sorry for any inconvenience.
Comment 11 Michal Sekletar 2017-10-13 07:12:06 EDT
(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).
Comment 17 errata-xmlrpc 2018-04-10 06:17:23 EDT
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

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