Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1362290

Summary: Ansible Upgrade Scripts don't account for DNS changes.
Product: OpenShift Container Platform Reporter: Eric Rich <erich>
Component: Cluster Version OperatorAssignee: Scott Dodson <sdodson>
Status: CLOSED WONTFIX QA Contact: Anping Li <anli>
Severity: low Docs Contact:
Priority: medium    
Version: 3.2.1CC: anli, aos-bugs, bleanhar, clichybi, jokerman, mmccomas, pep, sdodson, stwalter, vigoyal, xtian
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1362289 Environment:
Last Closed: 2019-01-31 16:00:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1362289, 1372452    
Bug Blocks:    

Description Eric Rich 2016-08-01 20:15:40 UTC 
+++ This bug was initially created as a clone of Bug #1362289 +++

Description of problem:

The following docs don't cover how to move existing nodes to the new prefered DNS configuration

https://docs.openshift.com/enterprise/3.2/install_config/upgrading/manual_upgrades.html
https://docs.openshift.com/enterprise/3.2/install_config/upgrading/automated_upgrades.html

The Upgrade steps / procedures should account for this.

Version-Release number of selected component (if applicable): 3.2 -> 3.2 

Additional info:

--- Additional comment from Eric Rich on 2016-08-01 16:14:32 EDT ---

https://github.com/openshift/openshift-ansible/blob/enterprise-3.2/playbooks/byo/openshift-cluster/enable_dnsmasq.yml 

Is likely one option to solve this.

However it is not currently in use.
Comment 1 Scott Dodson 2016-08-05 13:43:43 UTC 
I've tested but I'd like QE to validate. The playbook in playbooks/byo/openshift-cluster/enabled_dnsmasq.yml should enable dnsmasq on 3.2 or newer clusters.

ansible-playbook -i ~/ansible-ose playbooks/byo/openshift-cluster/enable_dnsmasq.yml
Comment 2 Anping Li 2016-08-10 12:03:58 UTC 
The pod build failed after run this task.

F0810 08:02:35.976518       1 builder.go:204] Error: build error: timeout while waiting for remote repository "https://github.com/openshift/cakephp-ex.git"
Comment 3 Scott Dodson 2016-08-10 12:08:49 UTC 
Anping,

On the host that ran this pod, can you try `dig @host-ip github.com` (where host-ip is the ip address of the host) and `systemctl status dnsmasq` or point me at the host so I can investigate?
Comment 11 Scott Dodson 2019-01-31 16:00:03 UTC 
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.