"flockerctl list-nodes" doesn't shows all the nodes

[akshaycalsoft]

Hello,
The Flocker Control Service node don't show all nodes.

I have 3 nodes

node1: All Flocker Agent Services are up. flocker-dataset-agent, flocker-container-agent and flocker-docker-plugin are running well. Ip address is 10.20.20.1
node2: All Flocker Agent Services are up. flocker-dataset-agent, flocker-container-agent and flocker-docker-plugin are running well. Ip address is 10.20.20.2
node-control (node control only): The Flocker Control Service is Up. flocker-control is running well. Ip address is 10.20.20.3
flockerctl list-nodes command shows:
[root@machine flocker]# flockerctl list-nodes
SERVER ADDRESS
56618826 10.20.20.1

I restarted both services, then I run flockerctl list-nodes command, still I don't see node2
[root@machine flocker]# flockerctl list-nodes
SERVER ADDRESS
56618826 10.20.20.1

I verified the certificates (node.crt and node.key) on both nodes whether they are different.

Any ideas?
Why I can not see another the node?
This question concerns Flocker Services?

[wallnerryan]

Usually we see this when the same node.crt/key is used on every node. Make sure each not has a different crt and key create separately.

e.g. 2 nodes

flocker-ca create-node-certificate node1
flocker-ca create-node-certificate node2

Can you verify this is the case?

Also, please run and send the output from the command flocker-diagnostics from the two nodes not showing up to [email protected].

[myechuri]

@akshaycalsoft : as @wallnerryan pointed out, can you please confirm if the node certificates are unique, and if so, can you please share output of flocker-diagnostics ? Thanks!

[akshaycalsoft]

Hi,
I verified that the node certificates on both the nodes are different.
I executed the flocker-diagnostic, but it is giving some error.

`[root@flocker-vm2 ~]# flocker-diagnostics

Failed to get data: Cannot assign requested address
WARNING: Usage of loopback devices is strongly discouraged for production use. Either use --storage-opt dm.thinpooldev or use --storage-opt dm.no_warn_on_loop_devices=true to suppress this warning.
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
fdisk: cannot open /dev/sdz: Input/output error
`

[akshaycalsoft]

@wallnerryan Please find attached zip file created by "flocker-diagnostics" command.
clusterhq_flocker_logs_1a42f148-3f8d-11e6-9eba-000c29bcba7c.zip