Comment 16 for bug 1897115

This is a symptom of the fact that vSphere does not implement subnet discovery.

When network-get runs, we attempt to resolve addresses in spaces via their subnets. When we can't do this, there is a fall-back to the unit's (via its machine) preferred local-cloud address.

In this case, after flannel comes up and the machine updates its link-layer devices and addresses, it changes the machine's preferred local cloud address, because it is in the RFC-1918 address space and the model's subnet is interpreted as public.

This can be resolved by implementing subnet discovery for vSphere, which I am investigating now.