DnsServers does not set resolvers properly

Bug #1716171 reported by Cédric Jeanneret deactivated
6
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
Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

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.

Revision history for this message
Cédric Jeanneret deactivated (cjeanneret-c2c-deactivated) wrote :

Hello,

Small update: setting only two resolver in the environment file does set them up both as expected.

Cheers,

C.

affects: tripleo → os-net-config
Changed in os-net-config:
milestone: queens-1 → none
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to os-net-config (master)

Related fix proposed to branch: master
Review: https://review.openstack.org/503532

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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-net-config (master)

Reviewed: https://review.openstack.org/503532
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=8ddab87c6ee2e80025e9340d806f93921779198b
Submitter: Jenkins
Branch: master

commit 8ddab87c6ee2e80025e9340d806f93921779198b
Author: Cédric Jeanneret <email address hidden>
Date: Wed Sep 13 07:37:22 2017 +0200

    Allow to pass more than two DNS while putting 2 DNS

    Until now, when we pass more than 2 DNS, only the first one is added in
    the ifcg-* config files.

    This patch-set proves the issue, and proves the correction actually works.

    Change-Id: I70a779782ab87cd4f74f3c50b0e649f503b386e3
    Closes-Bug: #1716171

Changed in os-net-config:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-net-config (stable/pike)

Fix proposed to branch: stable/pike
Review: https://review.openstack.org/504154

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-net-config (stable/pike)

Reviewed: https://review.openstack.org/504154
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=9ce34d529d7faa65cfa6f88aaecf735f92c4c89b
Submitter: Jenkins
Branch: stable/pike

commit 9ce34d529d7faa65cfa6f88aaecf735f92c4c89b
Author: Cédric Jeanneret <email address hidden>
Date: Fri Sep 15 00:13:39 2017 +0200

    Allow to pass more than two DNS while putting 2 DNS

    Until now, when we pass more than 2 DNS, only the first one is added in
    the ifcg-* config files.

    This patch-set proves the issue, and proves the correction actually works.

    Change-Id: I70a779782ab87cd4f74f3c50b0e649f503b386e3
    Closes-Bug: #1716171
    (cherry picked from commit 8ddab87c6ee2e80025e9340d806f93921779198b)

tags: added: in-stable-pike
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-net-config 7.3.1

This issue was fixed in the openstack/os-net-config 7.3.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/os-net-config 8.0.0

This issue was fixed in the openstack/os-net-config 8.0.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.