the fqdn in nova-compute pod will be incorrect if expose service before
apply openstack.
for example:
in nova-compute pod, it will get the fqdn
[root@compute-0 /]# hostname -A
192-188-204-33.centos.kube-system.svc.cluster.local
compute-0-cluster-host compute-0 compute-0
This will cause nova readness failure
Closes-Bug: 1893908
Change-Id: I85c34873528cca8fabf10ad7ddcb8997b23c8008
Signed-off-by: Austin Sun <email address hidden>
Reviewed: https:/ /review. opendev. org/749462 /git.openstack. org/cgit/ starlingx/ openstack- armada- app/commit/ ?id=13c8455b4ae 3a6a853df2be786 93df4f00964cf5
Committed: https:/
Submitter: Zuul
Branch: master
commit 13c8455b4ae3a6a 853df2be78693df 4f00964cf5
Author: Austin Sun <email address hidden>
Date: Wed Sep 2 23:14:02 2020 +0800
Disable use_fqdn as default for nova helm
the fqdn in nova-compute pod will be incorrect if expose service before 188-204- 33.centos. kube-system. svc.cluster. local 0-cluster- host compute-0 compute-0
apply openstack.
for example:
in nova-compute pod, it will get the fqdn
[root@compute-0 /]# hostname -A
192-
compute-
This will cause nova readness failure
Closes-Bug: 1893908 8fabf10ad7ddcb8 997b23c8008
Change-Id: I85c34873528cca
Signed-off-by: Austin Sun <email address hidden>