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.
There are a couple things that we could do to fix this
1. Create a wrapper for /etc/init.d/ntpdate that detects whether the network is up or not, and if so, then call the original version to start the script.
2. ntpdate appears to run only if the value of NETWORKING in /etc/sysconfig/network is set to yes. Setting this to No and updating the value when networking is configured either in manual or autoinstall could work, but more research needs to be done to determine whether setting NETWORKING to no out of the box causes any other side effects.
Recommend moving to 6.2 since this is a minor issue.
Created attachment 518311[details]
Patch
Disable networking by default in the image
Explicitly enable it when configuring a NIC in TUI
Enable when configuring network in autoinstall
start or restart ntp services after configuration in TUI
Verified on 6.2-0.14:
1. clean install via TUI and reboot.
2. no ntp boot fail on boot process, ntp does not start during boot.
3. login with admin and drop to shell, check ntpd is stopped.
4. exit and configure network.
5. drop to shell, check ntpd is running now.
6. reboot, can see ntp starting normal during boot process.
no other side effect found, set bug to be verified.
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.
http://rhn.redhat.com/errata/RHBA-2011-1783.html