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:
In case administrator makes a typo in a service definition, i.e.
{{{
[Install]
WantedBy=multiuser.target
}}}
then when enabling the service via "systemctl enable <service>" systemctl should kindly warn the poor admin that the requested target (multiuser vs multi-user) does not exist and hence the service will NOT be started automatically.
These errors are quite hard to debug so I think SystemD should do some basic checks.
How reproducible:
always
Actual results:
systemctl blindly creates a link for the not existing target
Expected results:
systemctl should warn the admin that the target does not exist, hence the service can not be enabled
Additional info:
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 (systemd bug fix and enhancement update), 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-2021:4469
Description of problem: In case administrator makes a typo in a service definition, i.e. {{{ [Install] WantedBy=multiuser.target }}} then when enabling the service via "systemctl enable <service>" systemctl should kindly warn the poor admin that the requested target (multiuser vs multi-user) does not exist and hence the service will NOT be started automatically. These errors are quite hard to debug so I think SystemD should do some basic checks. How reproducible: always Actual results: systemctl blindly creates a link for the not existing target Expected results: systemctl should warn the admin that the target does not exist, hence the service can not be enabled Additional info: