Bug 2219723
| Summary: | lack of `After=network-online.target` in ypbind.service cause timeout in system boot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Kazuo Moriwaka <kmoriwak> |
| Component: | ypbind | Assignee: | Ondřej Sloup <osloup> |
| Status: | CLOSED MIGRATED | QA Contact: | RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.8 | CC: | mmuzila |
| Target Milestone: | rc | Keywords: | MigratedToJIRA |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-20 18:10:10 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: | |||
|
Description
Kazuo Moriwaka
2023-07-05 01:18:07 UTC
Description of problem: ypbind.service fails by timeout, but it counts in network initialization Version-Release number of selected component (if applicable): RHEL 8 ypbind 2.5-2.el8 How reproducible: Always Steps to Reproduce: 1. RHEL 8slow network initialization environment 2. systemctl enable ypbind.service 3. reboot Actual results: Jul 04 11:12:57 hostname ypbind[1091]: Binding NIS service <<=== start ypbind.service before network online Jul 04 11:12:57 hostname systemd[1]: Starting Network Manager Wait Online... [...] Jul 04 11:17:48 hostname systemd[1]: Started Network Manager Wait Online. Jul 04 11:17:48 hostname systemd[1]: Reached target Network is Online. Jul 04 11:17:49 hostname ypbind[1445]: Binding took 292 seconds <<=== most of 292 sec is network initialization. It is >= 45 sec NISTIMEOUT. Jul 04 11:17:49 hostname ypbind[1453]: NIS server for domain example.com is not responding. Jul 04 11:17:49 hostname ypbind[1455]: Killing ypbind with PID 1050. Jul 04 11:17:49 hostname ypbind[1464]: Try increase NISTIMEOUT in /etc/sysconfig/ypbind Jul 04 11:17:49 hostname systemd[1]: ypbind.service: Control process exited, code=exited status=1 Jul 04 11:17:49 hostname systemd[1]: ypbind.service: Failed with result 'exit-code'. Expected results: Timeout shouldn't count in network initialization Additional info: In ypbind.service ``` Wants=nss-user-lookup.target network-online.target After=syslog.target rpcbind.service ypserv.service ``` I suggest change these lines as following: ``` Wants=nss-user-lookup.target After=syslog.target rpcbind.service ypserv.service network-online.target ``` This probelem is RHEL 8 only. At RHEL 7 ypbind.service, it has `After=NetworkManager-online.service`. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |