sos reports should collect all necessary gd2 logs - Githubissues

gluster / glusterd2

[DEPRECATED] Glusterd2 is the distributed management framework to be used for GlusterFS.

GNU General Public License v2.0

167 stars 82 forks source link

sos reports should collect all necessary gd2 logs #1448

Open PrasadDesala opened 5 years ago

PrasadDesala commented 5 years ago

Observed behavior

sos reports is not collecting glusterd2, bricks, glustershd logs.

Expected/desired behavior

sos reports should collect all necessary gd2 logs required for debugging.

Details on how to reproduce (minimal and precise)

1) Deploy a 3 node gcs system using vagrant. 2) Run sosreport

Information about the environment:

Glusterd2 version used (e.g. v4.1.0 or master): v6.0-dev.94.git601ba61
Operating system used: Centos
Glusterd2 compiled from sources, as a package (rpm/deb), or container: Container
Using External ETCD: (yes/no, if yes ETCD version): yes
If container, which container image:
Using kubernetes, openshift, or direct install:
If kubernetes/openshift, is gluster running inside kubernetes/openshift or outside: kubernetes

atinmu commented 5 years ago

We need to enhance https://github.com/sosreport/sos/blob/master/sos/plugins/gluster.py to ensure (a) glusterd2 log path is covered & (b) all the required commands are successfully triggered with glustercli. The plugin has to work based on if the configured gluster management daemon is either GD1 or GD2. Getting (b) to work is difficult as the plugin is run from the host not the gluster pods. Even with current stack (GD1, heketi based containerized storage), this is broken now.