Bug 990788
Summary: | authconfig cause service rpcbind restart, and registered rpc server lost. | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | JianHong Yin <jiyin> | |
Component: | authconfig | Assignee: | Tomas Mraz <tmraz> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | David Spurek <dspurek> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.0 | CC: | dspurek, ebenes, jiyin, pvrabec | |
Target Milestone: | rc | Keywords: | Reopened, TestBlocker | |
Target Release: | 7.0 | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | authconfig-6.2.6-5.el7 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 990790 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-13 10:59:17 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: | 990790 |
Description
JianHong Yin
2013-08-01 02:58:37 UTC
What are the reasons for this bug being a "TestBlocker" please? (In reply to Peter Vrabec from comment #1) > What are the reasons for this bug being a "TestBlocker" please? It cause our some nfs test(with nis) case run fail. I can debug and change the case code to avoid. However, this increases our workload. I am sorry but this is not a real bug. You can either call the authconfig with --nostart option if you do not want it to restart the services or you can restart the nfs after authconfig. (In reply to Tomas Mraz from comment #3) > I am sorry but this is not a real bug. You can either call the authconfig > with --nostart option if you do not want it to restart the services or you > can restart the nfs after authconfig. I do not think that. 1. First. In RHEL5 it work fine: just start nis bind, not restart the rpcbind server. 2. what do you think about if you start a server based rpc, then you find that all other server registered in rpcbind can not work. Obviously, that's wrong. OK, that makes sense, we can change authconfig to start the rpcbind and never stop it. Although in RHEL-5 authconfig restarts portmapper which is probably a problem as well. (In reply to Tomas Mraz from comment #5) > OK, that makes sense, we can change authconfig to start the rpcbind and > never stop it. Although in RHEL-5 authconfig restarts portmapper which is > probably a problem as well. ok, thanks; BTW: I test in RHEL-5.9, authconfig just start the ypbind, not restart portmapper; so maybe the action of restart rpcbind/portmapper is introduced at RHEL6+ ,, This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request. |