juju reload-spaces doesn't update DNS or GW values in unit netplan.

[Mirek]

Probably missing feature rather than a bug, but currently if for example, you have two GW or DNS servers in two different MAAS spaces, one is there by mistake. Once the model is deployed there is no way to fix it. When you fix it in MAAS and do juju reload-spaces the GW configuration is still there. As a test I've made a manual change in LXD container and rebooted file /etc/netplan/99-juju.yaml is re-created with old DNS info. If is not possible at the moment could we add it in and also where in juju database I could change it manually so I could update it without rebooting production deployment?

Thanks

[John A Meinel (jameinel)]

I don't know that we will grow the support to rewrite the host machine's networking. However, there aren't any other agents running there to update that configuration. I believe for LXD containers we might be reading the host machines configuration to figure out what to set for the containers, rather than making a separate request to MAAS to find out what the current information is.

[Mirek (mirek186)]

Yes, correct Juju agent is reading config from Juju DB and creating netplan out of it, I've tried to change MAAS config and run reload-spaces but Juju won't update that info. I think all we need is a way for juju to refresh all network info from MAAS, similar to reload-spaces but to fetch all information, otherwise, if you have to make an infrastructure change your only option is to keep manually changing LXD info after each reboot or rebuild the whole model, otherwise, Juju will overwrite LXD netplan with Juju database values.

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.