Bug 1372026 - openshift_use_flannel=true does not work properly
Summary: openshift_use_flannel=true does not work properly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.2.1
Assignee: Andrew Butcher
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 18:01 UTC by Scott Dodson
Modified: 2017-01-04 06:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously the installer did not properly configure an environment for flannel when openshift_use_flannel was set to true. We've corrected those errors and the installer will now correctly deploy environments using flannel.
Clone Of:
Environment:
Last Closed: 2016-09-12 17:36:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:1853 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 3.2 security update and bug fix update 2016-09-12 21:33:16 UTC

Description Scott Dodson 2016-08-31 18:01:24 UTC 
There were various problems when using openshift_use_flannel=true in the 3.2 installer. 

See https://github.com/openshift/openshift-ansible/issues/2326 and https://github.com/openshift/openshift-ansible/issues/2322
Comment 1 Scott Dodson 2016-08-31 18:02:45 UTC 
https://github.com/openshift/openshift-ansible/pull/2392
Comment 3 Gaoyun Pei 2016-09-01 08:50:24 UTC 
Verify this bug with openshift-ansible-3.2.28-1.git.0.5a85fc5.el7.noarch.rpm

Flannel network could be installed successfully with setting the following options in ansible inventory:
openshift_use_openshift_sdn=false
openshift_use_flannel=true

After installation, flanneld service is running, could connect to etcd cluster. No problems found in flannel configuration.

Router and docker-registry service also could be deployed, move this bug to verified.
Comment 5 errata-xmlrpc 2016-09-12 17:36:48 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/RHSA-2016:1853
Note You need to log in before you can comment on or make changes to this bug.