After reboot of GD2 pod, rebooted pod brick went to offline

[rmadaka]

1. Create pvc
2. Login to GD2 pod which is having bricks.
3. perfrom "reboot" command
4. After reboot, rebooted gd2 pod bricks went to offline, those bricks not coming back to online.

output:

+--------------------------------------+-------------------------------+---------------------------------------------------------------------+--------+-------+-----+
|               BRICK ID               |             HOST              |                                PATH                                 | ONLINE | PORT  | PID |
+--------------------------------------+-------------------------------+---------------------------------------------------------------------+--------+-------+-----+
| 3d1c57ee-8072-44a6-912e-8df32bc79ac2 | gluster-kube2-0.glusterd2.gcs | /var/run/glusterd2/bricks/pvc-d3006e55dce511e8/subvol1/brick1/brick | false  |     0 |   0 |
| 49b4d49e-1c4d-4f26-9977-b1c181b89f55 | gluster-kube3-0.glusterd2.gcs | /var/run/glusterd2/bricks/pvc-d3006e55dce511e8/subvol1/brick2/brick | true   | 43326 | 511 |
| 1ce6115b-f4c3-4d49-94f0-edb1edc13d58 | gluster-kube1-0.glusterd2.gcs | /var/run/glusterd2/bricks/pvc-d3006e55dce511e8/subvol1/brick3/brick | true   | 43251 |  65 |
+--------------------------------------+-------------------------------+---------------------------------------------------------------------+--------+-------+-----+

Log:

time="2018-10-31 09:13:33.990278" level=error msg="registry.SearchByBrickPath() failed for brick" brick=/var/run/glusterd2/bricks/pvc-d3006e55dce511e8/subvol1/brick1/brick error="SearchByBrickPath: port for brick /var/run/glusterd2/bricks/pvc-d3006e55dce511e8/subvol1/brick1/brick not found" source="[rpc_prog.go:104:pmap.(*GfPortmap).PortByBrick]"
time="2018-10-31 09:13:33.990778" level=info msg="client disconnected" address="10.233.65.9:977" server=sunrpc source="[server.go:109:sunrpc.(*SunRPC).pruneConn]"
~

[aravindavk]

Please provide the output of rpm -qa | grep gluster(issue may be related to gluster/glusterd2#1277)

[rmadaka]

[root@gluster-kube1-0 /]# rpm -qa | grep gluster
glusterfs-libs-6dev-0.184.gitff18121.el7.x86_64
glusterfs-client-xlators-6dev-0.184.gitff18121.el7.x86_64
glusterfs-cli-6dev-0.184.gitff18121.el7.x86_64
glusterd2-5.0-0.dev.el7.x86_64
glusterfs-6dev-0.184.gitff18121.el7.x86_64
glusterfs-api-6dev-0.184.gitff18121.el7.x86_64
glusterfs-fuse-6dev-0.184.gitff18121.el7.x86_64
glusterfs-server-6dev-0.184.gitff18121.el7.x86_64

[atinmu]

@rmadaka can you please retest this? Seems like this is fixed through gluster/glusterd2#1277.

[atinmu]

Kindly retest, closing this.