When Peer probed using API's, the online parameter shows "False"

[Shrivaibavi]

Observed behavior

[root@dhcp35-30 ~]# cat peer_add.json 
{ 
"addresses": ["dhcp35-240.lab.eng.blr.redhat.com"]
}

[root@dhcp35-30 ~]# curl -X POST http://localhost:24007/v1/peers --data @peer_add.json -H 'Content-Type: application/json'
{"id":"b7bd3edf-bbaf-4dec-af86-3f369ad1fb8e","name":"dhcp35-240.lab.eng.blr.redhat.com","peer-addresses":["dhcp35-240.lab.eng.blr.redhat.com:24008","10.70.35.240:24008"],"client-addresses":["127.0.0.1:24007","10.70.35.240:24007"],"online":false,"metadata":{"_zone":"b7bd3edf-bbaf-4dec-af86-3f369ad1fb8e"}}

Expected/desired behavior

As the peer probe is successful, Can we expect the online parameter to show as True ?

Details on how to reproduce (minimal and precise)

Information about the environment:

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

Other useful information

• glusterd2 config files from all nodes (default /etc/glusterd2/glusterd2.toml)
• glusterd2 log files from all nodes (default /var/log/glusterd2/glusterd2.log)
• ETCD configuration
• Contents of uuid.toml from all nodes (default /var/lib/glusterd2/uuid.toml)
• Output of statedump from any one of the node

Useful commands

• To get glusterd2 version

  glusterd2 --version
  

• To get ETCD version

  etcd --version
  

• To get output of statedump

  curl http://glusterd2-IP:glusterd2-Port/statedump