-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
Proposed
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The issue was found during testing PR pre-merge testing CNCC PR184 (which is for aws fix capacity issue), create this to track for gcp isue.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Build gcp cluster, check the node ip capacity, label one node as egress node.
{code:java}
Annotations: cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]
2. Create 101 EIPs
bash-3.2$ oc get cloudprivateipconfigs -ocustom-columns=NAME:.metadata.name,NODE:.spec.node,STATE:.status.conditions[].reason | grep CloudResponseSuccess | wc -l
100
bash-3.2$ oc get cloudprivateipconfigs -ocustom-columns=NAME:.metadata.name,NODE:.spec.node,STATE:.status.conditions[].reason | grep CloudResponseError
bash-3.2$ oc get cloudprivateipconfigs -ocustom-columns=NAME:.metadata.name,NODE:.spec.node,STATE:.status.conditions[].reason | grep CloudResponseError | wc -l
0
3. Reboot the egress node, wait the node up, got 79 IPs assigned, ip capacity sometimes changed.
bash-3.2$ oc get cloudprivateipconfigs -ocustom-columns=NAME:.metadata.name,NODE:.spec.node,STATE:.status.conditions[].reason | grep CloudResponseError | wc -l
0
bash-3.2$ oc get cloudprivateipconfigs -ocustom-columns=NAME:.metadata.name,NODE:.spec.node,STATE:.status.conditions[].reason | grep CloudResponseSuccess | wc -l
79
I1023 08:08:54.929332 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:25:57.952843 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:25:58.236892 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:25:58.462003 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:27:52.928596 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":92}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:27:53.157024 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":92}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:27:54.240961 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":92}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:27:54.423564 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":92}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:28:10.449442 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":93}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
I1023 08:28:14.303674 1 node_controller.go:152] Setting annotation: 'cloud.network.openshift.io/egress-ipconfig: [{"interface":"nic0","ifaddr":{"ipv4":"10.0.128.0/17"},"capacity":{"ip":100}}]' on node: huirwang-1023a-4nbtt-worker-c-wjwgh
Actual results:{code:none}
Some EIPs are not assigned back correctly, and ip capacity changed
Expected results:
All the EIPs assigned back to the nodes correctly and IP capacity not changed.
Additional info: