tripleo job are overwriting nameserver with 8.8.8.8

Bug #1711262 reported by Paul Belanger on 2017-08-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Critical
Sagi (Sergey) Shnaidman
Changed in tripleo:
importance: Undecided → High
status: New → Triaged
assignee: nobody → Emilien Macchi (emilienm)
milestone: none → pike-rc1
wes hayutin (weshayutin) on 2017-08-17
Changed in tripleo:
assignee: Emilien Macchi (emilienm) → nobody
assignee: nobody → Sagi (Sergey) Shnaidman (sshnaidm)
importance: High → Critical
tags: added: alert ci quickstart

@Paul, yes, it always was the case - to use 8.8.8.8 as DNS. So what do you suggest to use instead of it?

wes hayutin (weshayutin) wrote :

<pabelanger> undercloud_nameservers = 8.8.8.8
<pabelanger> that is wrong
<pabelanger> we need to stop defaulting to google DNS
* itlinux (~textual@2602:30a:c0aa:3fb0:99d6:ce31:d40a:e76d) has joined
<pabelanger> and use unbound service with is 127.0.0.1

Paul Belanger (pabelanger) wrote :

This hasn't always been this, for some reason it keeps getting changed back to google DNS which results in rate limiting and DNS failures.

For now, you shouldn't need to manage DNS on nodes from nodepool, we spend a lot of effort making sure they are using our local unbound service which is configured as forward zones.

I would suggest either removing your logic to stop managing DNS or also set it to 127.0.0.1.

This also applies to any nodes you are launching in the overcloud, all DNS requests should be hitting unbound first, not google.

Happy to talk more about this in IRC.

Changed in tripleo:
status: Triaged → Fix Released
tags: removed: alert
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers