Bug 1396990

Summary:	openshift-ansible DNS role uses hardcoded /24 subnet
Product:	OpenShift Container Platform	Reporter:	Jan Provaznik <jprovazn>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Status:	CLOSED WONTFIX	QA Contact:	Johnny Liu <jialiu>
Severity:	low	Docs Contact:
Priority:	low
Version:	3.4.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	aos-scalability-34
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-09 03:26:58 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:

Description Jan Provaznik 2016-11-21 10:53:32 UTC

Description of problem:
DNS role of openshift-ansible uses hardcoded /24 subnet range for setting access restriction. If openshift cluster nodes use other than /24 subnet then DNS doesn't work properly.

Upstream bug:
https://github.com/openshift/openshift-ansible/issues/2812

Comment 1 Scott Dodson 2017-02-10 03:06:06 UTC

What's the supported use case for this role? It's not included in any of the supported playbooks.

Comment 2 Jan Provaznik 2017-02-10 08:05:37 UTC

It's used in openshift-on-openstack for setting up DNS server - https://github.com/redhat-openstack/openshift-on-openstack/blob/master/templates/var/lib/ansible/playbooks/dns.yml#L43