/etc/resolv.conf is not updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas-deployer |
Fix Released
|
Medium
|
Nobuto Murata |
Bug Description
After the deployment, /etc/network/
[vmaas/
...
14 # Configure the dns nameservers
15 echo "Configuring the DNS nameserver"
16 for dev in `ip link show | grep eth.*mtu | cut -d':' -f2`; do
17 sudo resolvconf -d $dev
18 done
19
20 sudo sed -i 's/dns-
21 sudo resolvconf -u
...
I belivieve the pair of "resolvconf -d eth0.inet && resolvconf -a eth0.inet" is needed to update /etc/resolv.conf properly.
Related branches
- MAAS Deployers: Pending requested
-
Diff: 16 lines (+1/-2)1 file modifiedmaas_deployer/vmaas/templates/config-maas.sh (+1/-2)
- Billy Olsen: Approve
-
Diff: 136 lines (+21/-34)3 files modifiedmaas_deployer/vmaas/engine.py (+19/-16)
maas_deployer/vmaas/maasclient/clidriver.py (+1/-1)
maas_deployer/vmaas/templates/config-maas.sh (+1/-17)
tags: | added: cpec |
Changed in maas-deployer: | |
importance: | Undecided → Medium |
milestone: | none → 0.0.2 |
Changed in maas-deployer: | |
assignee: | nobody → Nobuto Murata (nobuto) |
status: | New → In Progress |
Changed in maas-deployer: | |
status: | In Progress → Fix Committed |
Changed in maas-deployer: | |
status: | In Progress → Fix Committed |
Changed in maas-deployer: | |
status: | Fix Committed → Fix Released |
A quick workaround is `sudo ifdown eth0 && sudo ifup eth0` or just reboot.