Bug 1325050 - Fail to test dns resolution when configuring dnsmasq on node
Summary: Fail to test dns resolution when configuring dnsmasq on node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-08 05:02 UTC by Ma xiaoqiang
Modified: 2016-07-04 00:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 16:40:28 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1065 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-05-12 20:32:56 UTC

Description Ma xiaoqiang 2016-04-08 05:02:29 UTC
Description of problem:
Fail to test dns resolution when configuring  dnsmasq on node



Version-Release number of selected component (if applicable):
https://github.com/sdodson/openshift-ansible -b cluster-dns


How reproducible:
always

Steps to Reproduce:
1. install env with dnsmasq on node

Actual results:
TASK: [openshift_node_dnsmasq | Test dns resolution] ************************** 
failed: [openshift-1.lab.eng.nay.redhat.com] => {"changed": false, "cmd": ["getent", "hosts", "google.com"], "delta": "0:00:00.004486", "end": "2016-04-07 23:35:51.601745", "rc": 2, "start": "2016-04-07 23:35:51.597259", "warnings": []}
failed: [openshift-2.lab.eng.nay.redhat.com] => {"changed": false, "cmd": ["getent", "hosts", "google.com"], "delta": "0:00:00.004238", "end": "2016-04-07 23:35:51.429506", "rc": 2, "start": "2016-04-07 23:35:51.425268", "warnings": []}
ok: [openshift-3.lab.eng.nay.redhat.com] => {"changed": false, "cmd": ["getent", "hosts", "google.com"], "delta": "0:00:00.073471", "end": "2016-04-07 23:35:51.545510", "rc": 0, "start": "2016-04-07 23:35:51.472039", "stderr": "", "stdout": "2404:6800:4003:c01::8a google.com", "warnings": []}

check by manual, the dns works fine.
It is better to try to test dns for several times

Expected results:
This step should succeed


Additional info:

Comment 1 Scott Dodson 2016-04-08 19:32:06 UTC
I've pushed a change that retries every second for up to 20 seconds. Please pull the latest and test.

Comment 2 Ma xiaoqiang 2016-04-11 01:01:28 UTC
Install env successfully, move this issue to VERIFIED.

Comment 3 Ma xiaoqiang 2016-04-11 02:28:10 UTC
The conditions for the dns port in the iptables didn't take effect.

Install ose-3.2 by default, check the iptables on the master
<--snip-->
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:8053
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            state NEW udp dpt:8053
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:53
ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            state NEW udp dpt:53
<--snip-->

the '53' and '8053' port are opened.

Comment 4 Ma xiaoqiang 2016-04-11 02:28:51 UTC
(In reply to Ma xiaoqiang from comment #3)
> The conditions for the dns port in the iptables didn't take effect.
> 
> Install ose-3.2 by default, check the iptables on the master
> <--snip-->
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
> dpt:8053
> ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            state NEW udp
> dpt:8053
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
> dpt:53
> ACCEPT     udp  --  0.0.0.0/0            0.0.0.0/0            state NEW udp
> dpt:53
> <--snip-->
> 
> the '53' and '8053' port are opened.

Add wrong comments.

Comment 6 errata-xmlrpc 2016-05-12 16:40:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1065


Note You need to log in before you can comment on or make changes to this bug.