Bug 970046 - PRD33 - gluster - Supporting RHS hooks through RHEV-M
Summary: PRD33 - gluster - Supporting RHS hooks through RHEV-M
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal (Show other bugs)
(Show other bugs)
Version: 3.3.0
Hardware: Unspecified Unspecified
Target Milestone: ---
: 3.3.0
Assignee: Sahina Bose
Whiteboard: gluster
Keywords: FutureFeature
Depends On: 850483
Blocks: 976616 1019470
TreeView+ depends on / blocked
Reported: 2013-06-03 11:30 UTC by Sahina Bose
Modified: 2016-02-10 18:58 UTC (History)
14 users (show)

Fixed In Version: is2
Doc Type: Enhancement
Doc Text:
Users can now manage Red Hat Storage hooks (volume lifecycle extensions) from the Red Hat Enterprise Virtualization Manager. The hooks are deployed during installation of Red Hat Storage servers in a cluster. The functions available to users are enabling or disabling hooks, viewing hook content and resolving content conflict.
Story Points: ---
Clone Of: 850483
: 976616 (view as bug list)
Last Closed: 2014-01-21 17:25:31 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Gluster
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
scohen: Triaged+

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2014:0038 normal SHIPPED_LIVE Important: Red Hat Enterprise Virtualization Manager 3.3.0 update 2014-01-21 22:03:06 UTC
oVirt gerrit 18495 None None None Never

Comment 1 Gowrishankar Rajaiyan 2013-09-11 15:03:39 UTC
Please provide steps to verify.

Comment 2 Sahina Bose 2013-09-11 15:54:10 UTC
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.

Comment 3 SATHEESARAN 2013-09-26 01:56:31 UTC

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

Comment 4 Sahina Bose 2013-09-26 06:43:49 UTC

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.

Comment 5 SATHEESARAN 2013-09-26 07:31:38 UTC
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

Comment 6 Prasanth 2013-11-11 12:22:58 UTC
This has been Verified. 

Following are the related bugs identified during testing and cloned against RHEVM: 


Comment 7 Charlie 2013-11-28 00:26:06 UTC
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.

Comment 8 errata-xmlrpc 2014-01-21 17:25:31 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.


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