search

openshift / openshift-ansible

Install and config an OpenShift 3.x cluster
https://try.openshift.com
Apache License 2.0
2.17k stars 2.32k forks source link

OKD 3.11 internal DNS issues #10904

Closed xrow closed 4 years ago

xrow commented 5 years ago

Description

Provide a brief description of your issue here. For example:

I used a single node setup, but it should be reproduceable on all.

/etc/sysconfig/network-scripts/ifcfg-eno1 

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=eno1
UUID=e575b25c-7ca7-4264-a641-9f849f95f446
DEVICE=eno1
ONBOOT=yes
IPADDR=192.168.188.101
PREFIX=24
IPADDR1=192.168.188.120
PREFIX1=24
IPADDR2=192.168.188.121
PREFIX2=24
IPADDR3=192.168.188.122
PREFIX3=24
GATEWAY=192.168.188.1
#PEERDNS=no
#DNS1=192.168.159.1
Version

Please put the following version information in the code block indicated below.

[root@localhost ~]# ansible --version ansible 2.6.6 config file = /etc/ansible/ansible.cfg configured module search path = [u'/etc/ansible/library'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /bin/ansible python version = 2.7.5 (default, Jul 13 2018, 13:06:57) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]

If you're operating from a git clone:

returns nothing usefull, but I use 3.11

Steps To Reproduce
  1. add in DNS1=192.168.159.1
  2. reboot server
  3. Look at cat /etc/resolv.conf 
    Generated by NetworkManager
search i-lab.local
nameserver 127.0.0.1
Additional Information

if I comment out and reboot all is fine again.

xrow commented 5 years ago

also i figured out that 

PEERDNS=no
DNS1=192.168.159.1

will also work.

but just

DNS1=192.168.159.1

won`t

openshift-bot commented 4 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 4 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 4 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 4 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/openshift-ansible/issues/10904#issuecomment-665240492): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.