Bug 1650392 - Node can't post Ready status when using ipfailover and cloudprovider vSphere
Summary: Node can't post Ready status when using ipfailover and cloudprovider vSphere
Keywords:
Status: CLOSED DUPLICATE of bug 1668802
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Node
Version: 3.11.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.11.z
Assignee: Ryan Phillips
QA Contact: Sunil Choudhary
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-16 04:50 UTC by luxq
Modified: 2020-06-02 16:46 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-02 16:46:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description luxq 2018-11-16 04:50:41 UTC
Description of problem:
When I installed openshift okd 3.11 with vsphere cloud provider, everything worked fine until the ipfailover was added, the problem occurred,Node can't post Ready status.


master api full log here:

E1116 02:56:54.095820       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[address:10.6.0.197 type:InternalIP] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:56:54.105421       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[type:InternalIP address:10.6.0.197] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:56:54.133776       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[address:10.6.0.197 type:InternalIP] map[type:InternalIP address:10.6.0.192]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:56:54.159910       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[type:InternalIP address:10.6.0.197] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:56:54.183218       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[address:10.6.0.197 type:InternalIP] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:57:04.192781       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[type:ExternalIP address:10.6.0.197] map[address:10.6.0.192 type:ExternalIP] map[address:10.6.0.197 type:InternalIP] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:57:04.203555       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[type:ExternalIP address:10.6.0.192] map[address:10.6.0.197 type:InternalIP] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}
E1116 02:57:04.232610       1 status.go:64] apiserver received an error that is not an metav1.Status: &errors.errorString{s:"The order in patch list:\n[map[address:10.6.0.197 type:ExternalIP] map[address:10.6.0.192 type:ExternalIP] map[address:10.6.0.197 type:InternalIP] map[address:10.6.0.192 type:InternalIP]]\n doesn't match $setElementOrder list:\n[map[type:ExternalIP] map[type:InternalIP] map[type:ExternalIP] map[type:InternalIP] map[type:Hostname]]\n"}


Version-Release number of selected component (if applicable):
openshift okd 3.11 


How reproducible:
deploy ipfailover add keepalived vip at the nodes,or manual add another ip address using ifconfig ens192:1 add 10.6.0.197

Comment 2 Michael Gugino 2020-05-19 01:18:02 UTC
This issue does appear related to the cloud provider, rather the kubelet and/or the api.

Comment 4 Ryan Phillips 2020-06-02 16:46:16 UTC
This does look like a duplicate of 1668802. Closing.

*** This bug has been marked as a duplicate of bug 1668802 ***


Note You need to log in before you can comment on or make changes to this bug.