Bug 1502866
Summary: | 3.6 Nodes will not start with 3.7 master | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Eric Paris <eparis> | ||||||||
Component: | Networking | Assignee: | Dan Winship <danw> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | urgent | ||||||||||
Version: | 3.7.0 | CC: | aos-bugs, bbennett, danw, jupierce, sdodson, yadu | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | 3.7.0 | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | No Doc Update | |||||||||
Doc Text: |
undefined
|
Story Points: | --- | ||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2017-11-28 22:17:21 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: | |||||||||||
Attachments: |
|
Description
Eric Paris
2017-10-16 21:26:00 UTC
17:26 < danw> "oc edit clusternetwork default" and set the "network" and "hostsubnetlength" fields to match the values in clusterNetworks 17:26 < danw> it *might* re-break it every time you restart master though Created attachment 1339473 [details]
oc get clusternetwork default -o yaml
Created attachment 1339474 [details]
journal of failed node start
Created attachment 1339478 [details]
default clusternetwork after manual intervention
note the trailing 'network' and 'hostsubnetlength' fields which match the CIDR.
*** Bug 1499040 has been marked as a duplicate of this bug. *** Setup 3.6 env openshift v3.6.173.0.56 kubernetes v1.6.1+5115d708d7 upgrade master to 3.7 openshift v3.7.0-0.176.0 kubernetes v1.7.6+a08f5eeb62 3.6 nodes could start normally with 3.7 master. And the clusternetowrk works well too. # oc get node NAME STATUS AGE VERSION host-8-xxx.host.centralci.eng.rdu2.redhat.com Ready,SchedulingDisabled 2h v1.7.6+a08f5eeb62 host-8-yyy.host.centralci.eng.rdu2.redhat.com Ready 2h v1.6.1+5115d708d7 # oc get clusternetwork NAME CLUSTER NETWORKS SERVICE NETWORK PLUGIN NAME default 10.128.0.0/14:9 172.30.0.0/16 redhat/openshift-ovs-subnet 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-2017:3188 |