[R2.20-Build 17]: host DNS config is getting changed after container creation
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R2.20 |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher | |||
| Trunk |
Fix Committed
|
Critical
|
Ignatious Johnson Christopher | |||
| nova-docker |
Fix Committed
|
Undecided
|
Ignatious Johnson Christopher | |||
Bug Description
In docker hypervisor setup when we launch the container, it just uses the /etc/resolv.conf from host on the container and host DNS confiuration is getting changed after that.
NS config on compute node just after fresh provisioning:
root@nodec59:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.204.216.51
nameserver 172.29.147.60
nameserver 10.209.194.133
search englab.juniper.net juniper.net
after launching docker1 in subnet 1.1.1.0/24(through horizon) :
root@nodec59:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 1.1.1.2
nameserver 10.204.216.51
nameserver 172.29.147.60
search englab.juniper.net juniper.net
after this, DNS resolution fails on the host.
NS config on docker1(which is same as host config before instance creation):
ubuntu@
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.204.216.51
nameserver 172.29.147.60
nameserver 10.209.194.133
search englab.juniper.net juniper.net
after launching instance in subnet 2.2.2.0/24:
root@nodec59:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 1.1.1.2
nameserver 2.2.2.2
nameserver 10.204.216.51
search englab.juniper.net juniper.net
each time a new instance is created from a new subnet, resolv.conf on host is getting overwritten with entry of DNS server of the subnet.
As per docker documentation:
"Regarding DNS settings, in the absence of either the --dns=IP_ADDRESS... or the --dns-search=
| information type: | Proprietary → Public |
| Changed in nova-docker: | |
| assignee: | nobody → Ignatious Johnson Christopher (ijohnson-x) |
| Changed in nova-docker: | |
| status: | New → In Progress |
| tags: | added: releasenote |
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #1 |
| OpenContrail Admin (ci-admin-f) wrote | #2 |
| Ignatious Johnson Christopher (ijohnson-x) wrote Re: [R2.20-Build 17]: DNS configuration in docker container is wrong and host DNS config is getting changed too | #3 |
| Ignatious Johnson Christopher (ijohnson-x) wrote | #4 |
| Changed in nova-docker: | |
| status: | In Progress → Fix Committed |
| status: | Fix Committed → In Progress |
| tags: | removed: releasenote |
| summary: |
- [R2.20-Build 17]: DNS configuration in docker container is wrong and - host DNS config is getting changed too + [R2.20-Build 17]: host DNS config is getting changed after container + creation |
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova-docker (master) | #5 |
| Changed in nova-docker: | |
| status: | In Progress → Fix Committed |
Reviewed: https:/
Committed: http://
Submitter: Zuul
Branch: R2.20
commit 22ac9793701d084
Author: Ignatious Johnson Christopher <email address hidden>
Date: Fri May 22 16:33:26 2015 -0700
Removing veth interfaces if the contrainer launch failed
Closes-Bug: 1452151
Closes-Bug: 1454976
Using inet6 argument with ip command to configure ipv6 address to container
Closes-Bug: 1455616
Configure network using statically instead of using dhclient to avoid
it writting to the compute hosts resolv.conf
Closes-Bug: 1455168
Periodically check the vrouter agent conncetion and publish the port informaton to
the vrouter agent.
Closes-Bug: 1454655
Change-Id: I3f59055da0748d