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.

Bug 1553093

Summary: Incorrect reference to unit in rhel-readonly.service
Product: Red Hat Enterprise Linux 7 Reporter: Jeremy L. Gaddis <rhbz>
Component: initscriptsAssignee: David Kaspar // Dee'Kej <deekej>
Status: CLOSED ERRATA QA Contact: Daniel Rusek <drusek>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.4CC: deekej, drusek, initscripts-maint-list, rhbz
Target Milestone: rc   
Target Release: 7.6   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: initscripts-9.49.42-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 10:15:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1549689    
Attachments:
Description Flags
/usr/lib/systemd/system/rhel-readonly.service none

Description Jeremy L. Gaddis 2018-03-08 09:44:39 UTC
Description of problem:

  In "rhel-readonly.service", (I believe) there is an incorrect reference to another unit.

Version-Release number of selected component (if applicable):

  9.49.40-2.el7 (x86_64)

Additional info:

  $ grep ^Before= /usr/lib/systemd/system/rhel-readonly.service
  Before=shutdown.target emergency.service emergency.target systemd-tmpfiles-setup.service local-fs.target systemd-random-seed-load.service

There is no "systemd-random-seed-load.service" unit.

I believe that, instead, "Before=" should reference the "systemd-random-seed.service" unit (which does, in fact, exist).

(This appears to have no impact whatsoever and is indeed quite trivial but the incorrect reference should either be fixed or removed at some point.)

Comment 2 Jeremy L. Gaddis 2018-03-08 09:48:14 UTC
Created attachment 1405783 [details]
/usr/lib/systemd/system/rhel-readonly.service

/usr/lib/systemd/system/rhel-readonly.service from initscripts-9.49.40-2.el7.x86_64.rpm

Comment 3 Lukáš Nykrýn 2018-03-08 10:01:58 UTC
Yeah, the systemd-random-seed-load.service existed about five years ago, then it was renamed.

Comment 4 David Kaspar // Dee'Kej 2018-03-08 16:54:36 UTC
Pull-request submitted:
https://github.com/fedora-sysv/initscripts/pull/169

Comment 5 David Kaspar // Dee'Kej 2018-03-09 13:17:56 UTC
Pull-request was merged into rhel7-branch.

Comment 11 errata-xmlrpc 2018-10-30 10:15:57 UTC
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/RHBA-2018:3131