DnsServers does not set resolvers properly
Bug #1716171 reported by
Cédric Jeanneret deactivated
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
os-net-config |
Fix Released
|
Medium
|
Cédric Jeanneret deactivated |
Bug Description
Dear Stackers,
Apparently, there's an issue with the DnsServers parameters: it doesn't set the resolvers as expected.
Currently, we're deploying Pike on CentOS 7, and we're pushing three resolvers (our freeIPA servers).
Unfortunately, it seems only one resolver is added instead of three (ok, two, because RHEL systems don't support three).
Is it a known issue due to the said limitation on RHEL family? Shall we put only two resolvers in the parameter?
It would be great to tackle that one quickly, having only one resolver isn't really reliable (we detected that issue when the ipa instance went down a night…).
Thank you in advance !
Cheers,
C.
Changed in tripleo: | |
milestone: | none → queens-1 |
summary: |
- [Pike] DnsServers does not set resolvers properly + DnsServers does not set resolvers properly |
Changed in tripleo: | |
status: | New → Triaged |
tags: |
added: pike-backport-potential removed: dnsservers pike resolvers |
Changed in tripleo: | |
importance: | Undecided → Medium |
affects: | tripleo → os-net-config |
Changed in os-net-config: | |
milestone: | queens-1 → none |
Changed in os-net-config: | |
assignee: | nobody → Cédric Jeanneret (cjeanneret-c2c) |
status: | Triaged → In Progress |
Changed in os-net-config: | |
status: | In Progress → Confirmed |
status: | Confirmed → In Progress |
To post a comment you must log in.
Ah, should have opened that one in os-net-config project maybe? As the ifcfg* files in /etc/sysconfig/ network- scripts are generated by that python lib/script…
Note: I'd rather put a "high" importance for that kind of thing, as it might prevent a good deploy of the overcloud (and the undercloud, as it uses the same process).
Cheers,
C.