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:
Command service something.socket restart produces well-known message "Redirecting...", but with "something.socket.service".
Also this bug affects other unit types (see Additional info).

Bug has been introduces in 
https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel7-branch&id=c7d25db27dbab853c4ccda8c984d84a7ceaf881d

Version-Release number of selected component (if applicable):
initscripts-9.49.37-1.el7

How reproducible:
Always

Steps to Reproduce:
1. service systemd-journald.socket restart

Actual results:
Redirecting to /bin/systemctl restart  systemd-journald.socket.service

Expected results:
Redirecting to /bin/systemctl restart  systemd-journald.socket

Additional info:
# service systemd-journald.service restart
Redirecting to /bin/systemctl restart  systemd-journald.service.service
# service mnt-qa.mount restart
Redirecting to /bin/systemctl restart  mnt-qa.mount.service

Created attachment 1204771 [details]
patch

# rpm -q initscripts
initscripts-9.49.37-1.el7.x86_64

# service systemd-journald.socket restart
Redirecting to /bin/systemctl restart  systemd-journald.socket.service

# rpm -q initscripts
initscripts-9.49.38-1.el7.x86_64

# service systemd-journald.socket restart
Redirecting to /bin/systemctl restart systemd-journald.socket

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-2017:2286