Open mbukatov opened 5 years ago
The data comes from /nodes/UUID/NodeContext/fqdn
:
[root@mbukatov-usm1-server ~]# etcdctl --ca-file /etc/pki/tls/certs/ca-usmqe.crt --cert-file /etc/pki/tls/certs/etcd.crt --key-file /etc/pki/tls/private/etcd.key --endpoints https://${HOSTNAME}:2379 ls /nodes | xargs -I'{}' etcdctl --ca-file /etc/pki/tls/certs/ca-usmqe.crt --cert-file /etc/pki/tls/certs/etcd.crt --key-file /etc/pki/tls/private/etcd.key --endpoints https://${HOSTNAME}:2379 get '{}'/NodeContext/fqdn
10.37.169.35
10.37.169.62
mbukatov-usm1-gl5
mbukatov-usm1-gl1.example.com
mbukatov-usm1-gl2
mbukatov-usm1-gl4.example.com
fqdn field of
.clusters.nodes
Tendrl API reply doesn't always contain fqdn.Version of Tendrl
1.6.3
Steps to Reproduce
gluster pool list
and note thatHostname
column of each node contains either ip address, short name or fqdn./api/1.0/clusters
REST API calljq '.clusters[0].nodes[].fqdn' reply.json
Actual results
This is what gluster reports:
And this is the fqdn provided by Tendrl REST API:
Expected results
Either provide fqdn in the field, or rename the field to something else. This depends on the purpose of the field and how it's actually used by Tendrl web ui.
Note that fixing this without coordination with ui will likely break web ui of Tendrl.