Bug 1631792
| Summary: | OpenShift ansible installer doesn't work with Calico network plugin - OpenShift 3.10 | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | mikolaj.ciecierski |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.10.0 | CC: | aos-bugs, bmeng, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | 3.10.z | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The calico network plugin playbooks have been updated to work properly in 3.10 environments.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-10 09:27:09 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
mikolaj.ciecierski
2018-09-21 15:04:55 UTC
We're working with Tigera on a few 3.10 fixes for Calico. https://github.com/openshift/openshift-ansible/pull/10198 https://github.com/openshift/openshift-ansible/pull/9868 https://github.com/openshift/openshift-ansible/pull/9866 The correct set of patches is https://github.com/openshift/openshift-ansible/pull/9621 https://github.com/openshift/openshift-ansible/pull/9868 https://github.com/openshift/openshift-ansible/pull/10198 All of these changes are merged into openshift-ansible-3.10.51-1 which is going through QE now. Tested with openshift-ansible-3.10.57-1.git.0.787bf7c.el7.noarch The cluster with calico network can be setup without issues. # oc get po -n kube-system -o wide NAME READY STATUS RESTARTS AGE IP NODE calico-kube-controllers-868f5c896d-v7t9l 1/1 Running 0 2h 172.18.4.13 ip-172-18-4-13.ec2.internal calico-node-csgtd 2/2 Running 0 2h 172.18.4.13 ip-172-18-4-13.ec2.internal calico-node-s44sq 2/2 Running 0 2h 172.18.15.188 ip-172-18-15-188.ec2.internal calico-node-tmp5m 2/2 Running 0 2h 172.18.10.41 ip-172-18-10-41.ec2.internal # oc get po -n kube-proxy-and-dns -o wide NAME READY STATUS RESTARTS AGE IP NODE proxy-and-dns-vzwlg 1/1 Running 0 2h 172.18.4.13 ip-172-18-4-13.ec2.internal proxy-and-dns-x7ds2 1/1 Running 0 2h 172.18.10.41 ip-172-18-10-41.ec2.internal proxy-and-dns-xvndl 1/1 Running 0 2h 172.18.15.188 ip-172-18-15-188.ec2.internal # oc get node --show-labels NAME STATUS ROLES AGE VERSION LABELS ip-172-18-10-41.ec2.internal Ready master 2h v1.10.0+b81c8f8 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=m3.large,beta.kubernetes.io/os=linux,kubernetes.io/hostname=ip-172-18-10-41.ec2.internal,node-role.kubernetes.io/master=true,projectcalico.org/ds-ready=true ip-172-18-15-188.ec2.internal Ready <none> 2h v1.10.0+b81c8f8 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=m3.large,beta.kubernetes.io/os=linux,kubernetes.io/hostname=ip-172-18-15-188.ec2.internal,projectcalico.org/ds-ready=true,registry=enabled,role=node,router=enabled ip-172-18-4-13.ec2.internal Ready compute 2h v1.10.0+b81c8f8 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=m3.large,beta.kubernetes.io/os=linux,kubernetes.io/hostname=ip-172-18-4-13.ec2.internal,node-role.kubernetes.io/compute=true,projectcalico.org/ds-ready=true,role=node 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/RHBA-2019:0026 |