Previously, when a server was down, the error message that was returned did not contain the server name. As a consequence, identifying the server that is down using this error message was not possible. With this fix, the server is easily identifiable from the error message.
Created attachment 764555[details]
screenshot of error
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
Verified and works with the build rhsc-3.1.0-0.57.master.el6.noarch.
Create a hook manually in one of the node in the cluster and put the other node to maintenance state. Now click on resolve conflicts and click "ok"
UI displays an error saying "Error while executing action: Cannot add Gluster Hook. The server <servername> is not UP". Attaching the screenshot.
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-2015-1494.html
Comment 12Red Hat Bugzilla
2023-09-14 01:46:58 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Created attachment 764555 [details] screenshot of error 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