Bug 1024263 - [RHS-C] Error while executing action Add Gluster Hook: Internal Engine Error
[RHS-C] Error while executing action Add Gluster Hook: Internal Engine Error
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc (Show other bugs)
Unspecified Unspecified
high Severity high
: ---
: RHGS 2.1.2
Assigned To: Darshan
: ZStream
Depends On:
Blocks: 1028972
  Show dependency treegraph
Reported: 2013-10-29 05:11 EDT by Prasanth
Modified: 2015-05-13 12:31 EDT (History)
9 users (show)

See Also:
Fixed In Version: CB7
Doc Type: Bug Fix
Doc Text:
Previously, resolving Hook Conflicts by copying the hook to all the servers was throwing an error as correct hooks directory was not created. Now, with this update, changes are made to create proper path for hooks directory.
Story Points: ---
Clone Of:
: 1028972 (view as bug list)
Last Closed: 2014-02-25 02:57:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
screensot of error (144.44 KB, image/png)
2013-10-29 05:11 EDT, Prasanth
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 21017 None None None Never

  None (edit)
Description Prasanth 2013-10-29 05:11:11 EDT
Created attachment 817016 [details]
screensot of error

Description of problem:

Error while executing action Add Gluster Hook: Internal Engine Error

Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.2-0.21.beta1.el6_4

[root@vm10 1]# rpm -qa |grep glusterfs
[root@vm10 1]# rpm -qa |grep vdsm

How reproducible: Always

Steps to Reproduce:
1. Create a cluster and add 2 RHS U2 nodes
2. Select the cluster, click on the "Gluster Hooks" sub-tab and click on "Sync"
3. Now, go to one of the server and execute # rm -rf /var/lib/glusterd/hooks/1/*
4. Again click on "Sync" and now the hooks will be in "missing conflict" state.
5. Select any hook and click on "Resolve Conflicts"
6. Resolve Missing Hook Conflict using "Copy the hook to all the servers" option and click on OK.

Here you will see the error. 

Actual results: Resolve Missing Hook Conflict fails to create the proper hooks directory and hence fails. Following is what vdsm.log says

Thread-3123::ERROR::2013-10-29 14:30:41,707::BindingXMLRPC::993::vds::(wrapper) unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/BindingXMLRPC.py", line 979, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/gluster/api.py", line 53, in wrapper
    rv = func(*args, **kwargs)
  File "/usr/share/vdsm/gluster/api.py", line 267, in hookAdd
    hookData, hookMd5Sum, enable)
  File "/usr/share/vdsm/supervdsm.py", line 50, in __call__
    return callMethod()
  File "/usr/share/vdsm/supervdsm.py", line 48, in <lambda>
  File "<string>", line 2, in glusterHookAdd
  File "/usr/lib64/python2.6/multiprocessing/managers.py", line 740, in _callmethod
    raise convert_to_error(kind, result)
OSError: [Errno 2] No such file or directory: '/var/lib/glusterd/hooks/1/set/post/tmpwfVnUZ'
Thread-3124::DEBUG::2013-10-29 14:30:43,361::BindingXMLRPC::974::vds::(wrapper) client []::call hostsList with () {}

It basically created the "POST" directory in caps and hence failed. See below:

[root@vm10 set]# pwd

[root@vm10 set]# ll
total 4
drwxr-xr-x 2 root root 4096 Oct 29 14:29 POST

Expected results: Resolve hooks should create all the missing directories/files with proper name and permission.

Additional info: Screenshot is attached and sosreports will be attached soon.
Comment 2 Matt Mahoney 2013-11-12 13:56:51 EST
Verified in cb7.
Comment 3 Shalaka 2014-01-06 02:29:10 EST
Please review the edited DocText and confirm.
Comment 5 errata-xmlrpc 2014-02-25 02:57:17 EST
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.


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