Description of problem: We are running RHGS automation for a new build of 3.5. While testing it we observed that volume cannot get exported for nfs. Due to that our automation scripts are failing. We are block due to this issue. Log snip. #################### 2019-04-08 07:23:57,046 INFO (run) root.eng.blr.redhat.com (cp): gluster volume set testvol_replicated nfs.disable off --mode=script 2019-04-08 07:23:57,046 DEBUG (_get_ssh_connection) Retrieved connection from cache: root.eng.blr.redhat.com 2019-04-08 07:23:57,700 INFO (_log_results) [34;1mRETCODE (root.eng.blr.redhat.com): 0 [0m 2019-04-08 07:23:57,701 INFO (_log_results) [47;30;1mSTDOUT (root.eng.blr.redhat.com)... volume set: success [0m 2019-04-08 07:24:27,731 INFO (run) root.eng.blr.redhat.com (cp): showmount -e localhost 2019-04-08 07:24:27,732 DEBUG (_get_ssh_connection) Retrieved connection from cache: root.eng.blr.redhat.com 2019-04-08 07:24:27,807 INFO (_log_results) [34;1mRETCODE (root.eng.blr.redhat.com): 1 [0m 2019-04-08 07:24:27,808 INFO (_log_results) [31;1mSTDERR (root.eng.blr.redhat.com)... clnt_create: RPC: Program not registered [0m 2019-04-08 07:24:27,808 INFO (run) root.eng.blr.redhat.com (cp): showmount -e localhost | grep -w testvol_replicated 2019-04-08 07:24:27,808 DEBUG (_get_ssh_connection) Retrieved connection from cache: root.eng.blr.redhat.com 2019-04-08 07:24:27,865 INFO (_log_results) [34;1mRETCODE (root.eng.blr.redhat.com): 1 [0m 2019-04-08 07:24:27,866 INFO (_log_results) [31;1mSTDERR (root.eng.blr.redhat.com)... clnt_create: RPC: Program not registered [0m 2019-04-08 07:24:27,866 INFO (export_volume_through_nfs) Volume testvol_replicated is not exported as 'nfs' export #################### Version-Release number of selected component (if applicable): - RHGS How reproducible: - Always Steps to Reproduce: 1.Create a volume 2.Try to export for GNFS Actual results: clnt_create: RPC: Program not registered ( Output is of showmount -e after setting nfs.disable off) Expected results: - volume should get exported properly
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-2019:3249