I personally cannot reproducible it on my testbed. I created a manual provider env which also doesn't support network spaces, added vxlan interface and /32 address on it like what flannel does, and restarted jujud on the unit, but Juju still returns my expected IP address. So not sure what actually triggers this behavior. I've attached juju-crashdump above, but some details like actual IP addresses may differ since the customer retried deployments multiple times, but no luck.
Subscribing ~field-high.
I personally cannot reproducible it on my testbed. I created a manual provider env which also doesn't support network spaces, added vxlan interface and /32 address on it like what flannel does, and restarted jujud on the unit, but Juju still returns my expected IP address. So not sure what actually triggers this behavior. I've attached juju-crashdump above, but some details like actual IP addresses may differ since the customer retried deployments multiple times, but no luck.