-
Bug
-
Resolution: Won't Do
-
Normal
-
None
-
4.13
-
Important
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-12739. The following is the description of the original issue:
—
Description of problem:
The IPv6 VIP does not seem to be present in the keepalived.conf.
networking: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 - cidr: fd65:10:128::/56 hostPrefix: 64 machineNetwork: - cidr: 192.168.110.0/23 - cidr: fd65:a1a8:60ad::/112 networkType: OVNKubernetes serviceNetwork: - 172.30.0.0/16 - fd65:172:16::/112 platform: vsphere: apiVIPs: - 192.168.110.116 - fd65:a1a8:60ad:271c::1116 ingressVIPs: - 192.168.110.117 - fd65:a1a8:60ad:271c::1117 vcenters: - datacenters: - IBMCloud server: ibmvcenter.vmc-ci.devcluster.openshift.com
Version-Release number of selected component (if applicable):
4.13.0-0.nightly-2023-04-21-084440
How reproducible:
Frequently.
2 failures out of 3 attemps.
Steps to Reproduce:
1. Install vSphere dual-stack with dual VIPs, see above config 2. Check keepalived.conf for f in $(oc get pods -n openshift-vsphere-infra -l app=vsphere-infra-vrrp --no-headers -o custom-columns=N:.metadata.name ) ; do oc -n openshift-vsphere-infra exec -c keepalived $f -- cat /etc/keepalived/keepalived.conf | tee $f-keepalived.conf ; done
Actual results:
IPv6 VIP is not in keepalived.conf
Expected results:
vrrp_instance rbrattai_INGRESS_1 { state BACKUP interface br-ex virtual_router_id 129 priority 20 advert_int 1 unicast_src_ip fd65:a1a8:60ad:271c::cc unicast_peer { fd65:a1a8:60ad:271c:9af:16a9:cb4f:d75c fd65:a1a8:60ad:271c:86ec:8104:1bc2:ab12 fd65:a1a8:60ad:271c:5f93:c9cf:95f:9a6d fd65:a1a8:60ad:271c:bb4:de9e:6d58:89e7 fd65:a1a8:60ad:271c:3072:2921:890:9263 } ... virtual_ipaddress { fd65:a1a8:60ad:271c::1117/128 } ... }
Additional info:
See OPNET-207
- clones
-
OCPBUGS-12739 IPv6 ingress VIP not configured in keepalived on vSphere Dual-stack
- Closed
- is blocked by
-
OCPBUGS-12739 IPv6 ingress VIP not configured in keepalived on vSphere Dual-stack
- Closed
- links to