Bug 1396990 - openshift-ansible DNS role uses hardcoded /24 subnet
Summary: openshift-ansible DNS role uses hardcoded /24 subnet
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard: aos-scalability-34
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 10:53 UTC by Jan Provaznik
Modified: 2017-06-09 03:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-09 03:26:58 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.