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:
Some 3rd party legacy applications or home made scripts are still present and not yet ported to systemd units. If a customer did not embrace NetworkManager for network startup in rhel7, the adoption of RHEL8 is a massive change, and this has impacts also on the daemons startup.
Version-Release number of selected component (if applicable):
systemd-239-31.el8_2.2.x86_64
How reproducible:
Always
Steps to Reproduce:
1. have in rc-local a daemon that need to connect to the network or to bind to a specific ip
2. the rc-local unit is started when network.target is reached, but that does not ensure there's already a network connection or the desired ip (dhcp...)
Actual results:
if something in rc-local need to access the internet, or to bind to an ip not yet available, it will fail.
Expected results:
By ensuring rc-local is started after network-online.target is reached, we can prevent an entire set of failure for those customers who may be force to still use rc-local and not modern application, due to 3rd party vendors not reactive or not avail anymore (think about propietary apps not supported anymore) or internal lack of resources, while reducing the risks of startup failures.
This small change has no impact on apps already ported to systemd, and will not worsten the experience of those who use rc-local, but will avoid an entire set of failure for those customers that still have to support legacy apps
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