Created attachment 765162 [details] log Description of problem: When installing host to setup, rpcbind service is not started. It leads to failures when mounting nfs exports. Thread-30::ERROR::2013-06-24 15:18:15,578::hsm::2307::Storage.HSM::(connectStorageServer) Could not connect to storageServer Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2304, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 320, in connect return self._mountCon.connect() File "/usr/share/vdsm/storage/storageServer.py", line 215, in connect raise e MountError: (32, ";mount.nfs: rpc.statd is not running but is required for remote locking.\nmount.nfs: Either use '-o nolock' to keep locks local, or start statd.\nmount.nfs: an incorrect mount option was specified\n") Version-Release number of selected component (if applicable): rhevm-3.3.0-0.4.master.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Install a host to rhevm 2. Try to create NFS SD 3. Actual results: Fails due to not running rpcbind service Expected results: rpcbind is running and Additional info: otopi install log attached
If vdsm requires rpcbind service it should depend on that service, so when started so that dependencies. I can do this manually in hot-deploy, but I don't think it will be the currect approach. What do you think?
(In reply to Alon Bar-Lev from comment #1) > If vdsm requires rpcbind service it should depend on that service, so when > started so that dependencies. > > I can do this manually in hot-deploy, but I don't think it will be the > currect approach. > > What do you think? I think that you are right - just like vdsm starts iscsid, it should ensure nfs is started. Note, however, that it would be much nicer if iscid was a soft dependency, to be started only if iscsi-based storage domains are used. I am not sure why this is a TestBlocker, though - it is quite easy to enable rpcbind before installation begins.
*** Bug 978285 has been marked as a duplicate of this bug. ***
Also note that NFS v4 does not require rpcbind
is7. [root@tigris03 init.d]# ./rpcbind status rpcbind (pid 6433) is running... NFS export domain was successfully created and mounted.
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-2014-0040.html