+++ This bug was initially created as a clone of Bug #977355 +++ Description of problem: Following incorrect error message is seen during resolve conflict: --- Error while executing action: Cannot add Gluster Hook. The server ${VdsName} is not UP. --- Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.0-0.bb4.el6rhs How reproducible: 100% Steps to Reproduce: 1. Have a 2 node cluster 2. Manually create a hook in node1 so that a missing conflict is created and detected in node2. 3. Put node2 into Maintenance 4. Now click on Resolve conflicts; make sure the default option (Copy the hook to all the servers) is selected and click on OK Actual results: The following incorrect error is seen: --- Error while executing action: Cannot add Gluster Hook. The server ${VdsName} is not UP. --- Expected results: The error message should be proper Additional info: Screenshot attached --- Additional comment from RHEL Product and Program Management on 2013-06-24 07:38:23 EDT --- Since this issue was entered in bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. --- Additional comment from Dusmant on 2013-10-21 09:23:24 EDT --- Doc Text will be added, once bug fix required rate starts tapering... --- Additional comment from Dusmant on 2013-10-24 00:55:49 EDT --- Not in Corbett
Red Hat Enterprise Virtualization Manager Version: 3.3.0-0.31.beta1.el6ev
3.5.1 is already full with bugs (over 80), and since none of these bugs were added as urgent for 3.5.1 release in the tracker bug, moving to 3.5.2
Tested with RHGS 3.1.2 nightly ( glusterfs-3.7.1-17el7rhgs ) and RHEV 3.6.2.6 While repeating the steps mentioned in comment0, the error messages is thrown as "Error while executing action: Cannot add Gluster Hook. The server RHGS-Node-2 is not UP." Marking this bug as VERIFIED
Note : RHGS 3.1.2 has vdsm 4.16.z and it can't be added to RHEVM 3.6 So I have used the custom build vdsm & vdsm gluster of build 4.17.16 to add it to RHEV 3.6.2.6
You should be able to add RHGS 3.1.2 to a 3.5 cluster level in RHEV-M 3.6, and verify this.
(In reply to Sahina Bose from comment #9) > You should be able to add RHGS 3.1.2 to a 3.5 cluster level in RHEV-M 3.6, > and verify this. Tested and verified the same. Apologies for the late update