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
This issue does appear related to the cloud provider, rather the kubelet and/or the api.
This does look like a duplicate of 1668802. Closing. *** This bug has been marked as a duplicate of bug 1668802 ***