Container on sshprovided machine: incorrect DNS
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I've added a physical node via juju add-machine ssh:...
When building a container on this machine I'm getting issues with DNS resolution there, because resolv.conf gets populated with the hosts DNS entries first, and maas-dns only afterwards. Therefore resolving Maas provisioned machines fails.
The log also warns about this, from the machine log:
2019-03-25 20:43:43 WARNING juju.provisioner broker.go:107 no name servers supplied by provider, using host's name servers.
2019-03-25 20:43:43 WARNING juju.provisioner broker.go:107 no search domains supplied by provider, using host's search domains.
2019-03-25 20:43:43 WARNING juju.provisioner broker.go:115 incomplete DNS config found, discovering host's DNS config
2019-03-25 20:43:52 WARNING juju.provisioner broker.go:107 no name servers supplied by provider, using host's name servers.
2019-03-25 20:43:52 WARNING juju.provisioner broker.go:107 no search domains supplied by provider, using host's search domains.
2019-03-25 20:43:52 WARNING juju.provisioner broker.go:115 incomplete DNS config found, discovering host's DNS config
Bug #1819171 possibly related
Version info:
juju 2.5.3
Maas 2.3.5 / xenial
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Peter Sabaini (peter-sabaini) wrote | #2 |
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
Can you describe the situation with the manual machine. The code expects that if MAAS is the provider that the host machine is aware/using the MAAS dns and so the manual machine process messes up that logic. As a work around you'll have to have the manually added machine to the model have the DNS you are looking for.