Bug 1170400
| Summary: | race condition with dhcp causes ypbind to fail at boot | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Joe Pruett <joey> |
| Component: | ypbind | Assignee: | Petr Kubat <pkubat> |
| Status: | CLOSED ERRATA | QA Contact: | Tomas Dolezal <todoleza> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | hhorak, kvolny, mmuzila, pkubat, todoleza, wcolburn+bugzilla |
| Target Milestone: | rc | Keywords: | Patch |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ypbind-1.37.1-9.el7 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-01 23:07:30 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1346768, 1393868, 1400961 | ||
|
Description
Joe Pruett
2014-12-04 01:06:35 UTC
Sooo, I have this problem. I was going to file a ticket on it this morning, but I see this two year old ticket just languishing here, which doesn't inspire me with hope. Have you found a solution to work around the problem? I've tried addind systemd dependencies, but I can't make it work. I'm thinking of just rewriting the ypbind service to include a busy-loop that simply waits for the network to really be up before it tries to ypbind... (In reply to Schlake from comment #3) > Sooo, I have this problem. I was going to file a ticket on it this morning, > but I see this two year old ticket just languishing here, which doesn't > inspire me with hope. > > Have you found a solution to work around the problem? I've tried addind > systemd dependencies, but I can't make it work. I'm thinking of just > rewriting the ypbind service to include a busy-loop that simply waits for > the network to really be up before it tries to ypbind... i actually just ran into this again yesterday. i use kickstart for most installs, so i have just resorted to setting the nis domain staticly via kickstart configs. i was installing a non-kickstart machine and had to remember what i had done to get around this. someone at least seems to have looked at it in june, but it references a bug that isn't public. Unfortunately, we have three NIS domains and laptops need to float between them as they move around, so the DHCP functionality is critical for us. I spotted a typo in my RequiredBy= attempt, so I'm re-kicking now to see that helps. Otherwise I've written a new version of ypbind-pre-setdomain that does a busy loop for 10 seconds checking for the domainname to be set before giving up. Thanks though. Thank you for taking the time to report this issue to us. We appreciate the feedback and use reports such as this one to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to guarantee the timeliness or suitability of a resolution.
If this issue is critical or in any way time sensitive, please raise a ticket through the regular Red Hat support channels to ensure it receives the proper attention and prioritization to assure a timely resolution.
For information on how to contact the Red Hat production support team, please visit:
https://www.redhat.com/support/process/production/#howto
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/RHEA-2017:2202 |