DNS on deployed cluster doesn't respect DNS_UPSTREAM from astute.yaml
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Dennis Dmitriev |
Bug Description
Reproduced on CI: http://
When cluster deployed, DNS on controllers are configured without respecting the 'DNS_UPSTREAM' setting provided from /etc/fuel/
=== controller:
root@node-1:~# cat /etc/resolv.
nameserver 8.8.8.8
nameserver 8.8.4.4
===== admin node:
[root@nailgun ~]# cat /etc/fuel/
HOSTNAME: nailgun
DNS_DOMAIN: test.domain.local
DNS_SEARCH: test.domain.local
DNS_UPSTREAM: 10.109.15.1 8.8.8.8
....
As the result: it is impossible to access the intranet resources from the cloud using host names of the resources.
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov) |
Changed in fuel: | |
assignee: | Fuel QA Team (fuel-qa) → Dennis Dmitriev (ddmitriev) |
status: | Confirmed → In Progress |
I suppose this is because you have not specified this server as DNS server for the particular cluster - nailgun does not inherit such settings from settings.yaml, unfortunately.