Canonical Juju

  1. Bug #1897115
  2. Comment #3

Comment 3 for bug 1897115

Revision history for this message
Nobuto Murata (nobuto) wrote : Re: network-get returns /32 address and units cannot talk to each other

For example in 4/baremetal/var/log/juju/unit-kubeapi-load-balancer-0.log, initially 133.X.X.X address will be picked up by Juju:

2020-09-23 10:09:06 INFO juju-log Wrote vhost config {'host': '127.0.0.1', 'port': 443, 'server_name': '_', 'services': [{'service_name': 'kubernetes-master', 'hosts': [{'hostname': '133.X.X.X', 'private-address': '133.X.X.X', 'port': '6443'}, {'hostname': '172.16.8.0', 'private-address': '172.16.8.0', 'port': '6443'}]}], 'server_certificate': '/srv/kubernetes/server.crt', 'server_key': '/srv/kubernetes/server.key', 'proxy_read_timeout': 600} to apilb.conf

But once flannel is fully ready, Juju will push out 133.X.X.X address in favor of flannel's /32 address.

2020-09-23 10:23:18 INFO juju-log Wrote vhost config {'host': '127.0.0.1', 'port': 443, 'server_name': '_', 'services': [{'service_name': 'kubernetes-master', 'hosts': [{'hostname': '172.16.13.0', 'private-address': '172.16.13.0', 'port': '6443'}, {'hostname': '172.16.8.0', 'private-address': '172.16.8.0', 'port': '6443'}]}], 'server_certificate': '/srv/kubernetes/server.crt', 'server_key': '/srv/kubernetes/server.key', 'proxy_read_timeout': 600} to apilb.conf