Bug 1393970 - gdeploy: nfs-ganesha cluster creation fails while copying ganesha config files to shared storage
Summary: gdeploy: nfs-ganesha cluster creation fails while copying ganesha config file...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.2.0
Assignee: Sachidananda Urs
QA Contact: Arthy Loganathan
URL:
Whiteboard:
Depends On:
Blocks: 1351528
TreeView+ depends on / blocked
 
Reported: 2016-11-10 18:12 UTC by Arthy Loganathan
Modified: 2017-03-23 05:08 UTC (History)
5 users (show)

Fixed In Version: gdeploy-2.0.1-4
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 05:08:54 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:0482 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.2.0 gdeploy bug fix and enhancement update 2017-03-23 09:06:28 UTC

Description Arthy Loganathan 2016-11-10 18:12:29 UTC
Description of problem:
nfs-ganesha cluster creation fails while copying ganesha config files to shared storage

Version-Release number of selected component (if applicable):
gdeploy-2.0.1-3.el7rhgs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Setup nfs-ganesha using gdeploy.

Actual results:
nfs-ganesha cluster creation fails while copying ganesha config files to shared storage

Expected results:
nfs-ganesha cluster should get created successfully.

Additional info:
Getting two types of errors:

1)
TASK [Creating ganesha-ha.conf file] *******************************************
changed: [dhcp46-111.lab.eng.blr.redhat.com]
changed: [dhcp46-139.lab.eng.blr.redhat.com]
changed: [dhcp46-124.lab.eng.blr.redhat.com]
fatal: [dhcp46-115.lab.eng.blr.redhat.com]: FAILED! => {"changed": true, "failed": true, "msg": "Could not replace file: /root/.ansible/tmp/ansible-tmp-1478774817.35-18824176142499/source to /var/run/gluster/shared_storage/nfs-ganesha/ganesha-ha.conf: [Errno 2] No such file or directory"}
to retry, use: --limit
        @/tmp/tmpXpVkrx/ganesha-conf-create.retry

2)
fatal: [10.70.46.111]: FAILED! => {"changed": true, "failed": true, 
"msg": "Could not replace file: 
/root/.ansible/tmp/ansible-tmp-1378724718.57-18824172241273/source to 
/var/run/gluster/shared_storage/nfs-ganesha/ganesha-ha.conf: [Errno 117] 
Structure needs cleaning"} 

fatal: [10.70.46.115]: FAILED! => {"changed": true, "failed": true, 
"module_stderr": "", "module_stdout": "Traceback (most recent call 
last):\r\n  File \"/tmp/ansible_Vu_Jff/ansible_module_copy.py\", line 
364, in <module>\r\n    main()\r\n  File 
\"/tmp/ansible_Vu_Jff/ansible_module_copy.py\", line 343, in main\r\n 
module.atomic_move(b_mysrc, dest, 
unsafe_writes=module.params['unsafe_writes'])\r\n  File 
\"/tmp/ansible_Vu_Jff/ansible_modlib.zip/ansible/module_utils/basic.py\", line 
2017, in atomic_move\r\nOSError: [Errno 2] No such file or directory: 
'/var/run/gluster/shared_storage/nfs-ganesha/ganesha-ha.conf'\r\n", 
"msg": "MODULE FAILURE"}

Comment 2 Sachidananda Urs 2016-11-12 16:39:55 UTC
Arthy can you please double check if the proposed solution of making changes only in master_node work?

Comment 4 Arthy Loganathan 2016-11-14 10:47:19 UTC
I ran ganesha setup thrice with the proposed solution and its passed.

Comment 6 Sachidananda Urs 2016-11-14 10:58:00 UTC
Commit: https://github.com/gluster/gdeploy/pull/216/commits/c90489babe fixes the issue.

Comment 7 Arthy Loganathan 2016-11-21 12:12:48 UTC
Verified the fix in build, gdeploy-2.0.1-4.el7rhgs.noarch

Comment 9 errata-xmlrpc 2017-03-23 05:08:54 UTC
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://rhn.redhat.com/errata/RHEA-2017-0482.html


Note You need to log in before you can comment on or make changes to this bug.