Description of problem:
On a 4node cluster with glusterfs-3.8.4-52 and a tendrl server with below mentioned packages, if the gluster import fails for any reason, the tasks tab correctly displays the failure and the message. The field 'status' in Tasks shows as 'failed' - as expected.
The Clusters tab, however, shows all the hosts to be successfully imported, in other words, it shows all green --> giving no indication that the import has failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a 4node storage cluster with latest gluster 3.3.1 bits
2. Ran ansible playbook to setup webadmin and storage nodes
3. Enabled webadmin repos on all storage nodes, but for one
4. Import cluster on webadmin
Import fails as expected. Tasks correctly shows it. Clusters tab doesn't.
Information should be uniform across all tabs of webadmin. Showing all green on Clusters tab is misleading to the end user.
Update from Nishanth when this was shown to him - "The field 'managed' in Clusters tab is getting flipped to 'Yes', even when the import has failed.
The hosts of the cluster shown as green depends on the state of those hosts reported by tendrl-node-agents running on each of them.
What needs to be checked is whether the Cluster is marked with errors during the failed import correctly.
As mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1514423#c2, icon will be still green but appropriate error messages are shown on the UI. Also you will see the right menus and buttons based on the status of the cluster.
Created attachment 1357257 [details]
The cluster tab rightly depicts the status of the hosts and the cluster even when import fails
Under the clusters tab, when the cluster import fails, the hosts are marked with green but the cluster is down which is rightly depicted.
Adding the attachment.
Moving this bug to verified.
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.