Bug 1372026
| Summary: | openshift_use_flannel=true does not work properly | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> | 
| Component: | Installer | Assignee: | Andrew Butcher <abutcher> | 
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> | 
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.2.1 | CC: | aos-bugs, gpei, jokerman, jprovazn, mmccomas | 
| Target Milestone: | --- | ||
| Target Release: | 3.2.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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. 
 | 
        
        
        
        Story Points: | --- | 
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-12 17:36:48 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: | |||
| 
 
        
          Description
        
        
          Scott Dodson
        
        
        
        
        
          2016-08-31 18:01: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. 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  |