Bug 1023529 - [RHSC] Importing an existing cluster when one of the servers in the cluster is unresolvable or unreachable from the engine can be improved.
Summary: [RHSC] Importing an existing cluster when one of the servers in the cluster i...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhsc
Version: 2.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Nishanth Thomas
QA Contact: Shruti Sampat
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-25 15:58 UTC by Shruti Sampat
Modified: 2015-08-31 09:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-31 09:54:20 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Shruti Sampat 2013-10-25 15:58:59 UTC
Description of problem:
-----------------------

When one of the servers in a cluster is unresolvable or unreachable from the engine, and when the cluster is imported via the Console, the following behavior is seen -

* the Add Hosts screen shows only the servers that are resolvable/reachable from engine and those servers are imported.

The Add Hosts screen should show all the existing servers regardless of whether they are resolvable/reacahable and then only those shall be imported that can be reached and resolved. For those that cannot be imported, a pop-up should be shown to the user saying that these servers cannot be imported due to these reasons.

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

How reproducible:
Always

Steps to Reproduce:
-------------------

Case A 

1. For one of the nodes in the cluster, use a hostname that is only resolvable among the storage nodes and not from the engine, for peer probe ( can be done through an entry in the /etc/hosts file )
2. Import the cluster via the Console.

Case B

1. Power off one of the nodes in the cluster to make it unreachable from the engine.
2. Import the cluster via the Conole.

Actual results:
For both cases above, the above described behavior is seen.

Expected results:
Behavior can be improved as explained above.

Additional info:

Comment 4 Dusmant 2015-08-31 09:54:20 UTC
We are not planning to fix it. Hence closing this BZ. If you think, it's applicable for 3.x release and would have an impact on customer, pls. open up a new BZ with the appropriate version. Thanks, -Dusmant


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