Red Hat Bugzilla – Bug 970046
PRD33 - gluster - Supporting RHS hooks through RHEV-M
Last modified: 2016-02-10 13:58:48 EST
Please provide steps to verify.
Feature page for this at http://www.ovirt.org/Features/Gluster_Hooks_Management.
You could use the test cases developed by RHSC team to verify.
I was using RHEVM3.3 (IS15) on RHEL6.5 Beta.
I have a "gluster-cluster" of compatibility 3.2 containing RHS 2.1 Nodes.
I could see 'Host Hooks" subtab, when I select a particular RHS node.
But this sub-tab is empty. I couldn't see any hooks as described in http://www.ovirt.org/Features/Gluster_Hooks_Management
Please provide me more information for me to VERIFY this bug
The Host Hooks subtab is for VDSM hooks and not relevant in a gluster cluster.
To verify the Gluster hooks management feature, you need to add nodes to a 3.3 cluster as this version is available only in 3.3 cluster level.
You will need RHS 2.1 Update 2 nodes (Corbett) to do this.
This bug could not be VERIFIED, as it required RHS 2.1 update 2, as per comment4.
Since RHS 2.1 update 2 is not yet available, this could not be VERIFIED
This has been Verified.
Following are the related bugs identified during testing and cloned against RHEVM:
This bug is currently attached to errata RHEA-2013:15231. 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:
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.