Red Hat Bugzilla – Bug 965825
Cluster Service Sub Tab not displaying hosts
Last modified: 2016-04-18 06:06:11 EDT
Created attachment 751363 [details]
Description of problem:
Cluster Service Sub Tab shows not hosts.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create a cluster with 2 nodes
2. add a distributed volume using o and start the volume
3. navigate to the cluster main tab
4. click on the services sub tab
5. in the sub tab, in the host dropdown, select the first host and click filter.
no services displayed
services should be displayed such as samba, gluster, etc.
Versions: rhsc-2.1.0-0.bb1.el6rhs.noarch and RHS-2.1-20130515.n.0-RHS-x86_64-DVD1.iso
We are currently capturing the details of NFS and SHD(Self-heal daemon) services and show them on the ui.
NFS process will be running in the nodes only if a volume of the cluster supports nfs(nfs.disable=off). Also SHD will be running only if you have a Replicate volume.
Can you please provide the output of the following command in one of the storage nodes.
gluster volume status <volname>
I used a replicate volume with nfs.disabled=off but still can not get any information to display on the services sub tab.
I'm attaching a screenshot with output from from 'gluster volume status' and screenshot of from rhsc.
Created attachment 751666 [details]
screenshot with gluster status
Looks like there is no problem with the configuration.
Can you please attach the engine.log and vdsm.log files?
Created attachment 754820 [details]
engine log attached
Created attachment 754821 [details]
Can you please attach the vdsm.log files from the storage nodes as well?
Created attachment 756872 [details]
sorry about that...vdsm log attached.
Related to glusterfs bug where the server id is shown instead of ip in the volume status command.
Since you were filtering by host, there are no services shown in the list
*** Bug 973602 has been marked as a duplicate of this bug. ***
Moving to Modified as fix will be available in next RHS 2.1 respin
Fixed in bb6
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.