Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
ACM 2.7.0
-
False
-
None
-
False
-
No
Description
Description of problem:
ACM 2.7 / Submariner 0.14.0
Deployment consist two clusters:
- aws, ocp 4.10, SDN
- gcp, ocp 4.11, OVN
During execution of subctl diagnose all tests, the following gateway error appear:
• Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed ... ✗ Checking the firewall configuration to determine if intra-cluster VXLAN traffic is allowed ✗ Error: could not find the active Gateway node "ip-10-0-94-52" in local cluster "mbabushk-aws" ✗ Unable to obtain a gateway node: Error: could not find the active Gateway node "ip-10-0-94-52" in local cluster "mbabushk-aws"
The connection status of the gatways between clusters shown as ok:
Cluster "mbabushk-aws" • Detecting broker(s) ... ✓ Detecting broker(s) ✓ No brokers found • Showing Connections ... ✓ Showing Connections GATEWAY CLUSTER REMOTE IP NAT CABLE DRIVER SUBNETS STATUS RTT avg. mbabushk-gcp-c2vpx-submariner- mbabushk-gcp 34.82.141.220 yes libreswan 172.31.0.0/16, 10.132.0.0/14 connected 21.627312ms • Showing Endpoints ... ✓ Showing Endpoints CLUSTER ENDPOINT IP PUBLIC IP CABLE DRIVER TYPE mbabushk-aws 10.0.94.52 18.144.24.97 libreswan local mbabushk-gcp 10.0.128.4 34.82.141.220 libreswan remote • Showing Gateways ... ✓ Showing Gateways NODE HA STATUS SUMMARY ip-10-0-94-52 active All connections (1) are established • Showing Network details ... ✓ Showing Network details Discovered network details via Submariner: Network plugin: OpenShiftSDN Service CIDRs: [172.30.0.0/16] Cluster CIDRs: [10.128.0.0/14] • Showing versions ... ✓ Showing versions COMPONENT REPOSITORY VERSION submariner-gateway registry.redhat.io/rhacm2 v0.14.0 submariner-routeagent registry.redhat.io/rhacm2 v0.14.0 submariner-operator registry.redhat.io/rhacm2 3fd1f0ec672e20ea2d2645d1d4510413304ade3f470cde3507bce4672a943002 submariner-lighthouse-agent registry.redhat.io/rhacm2 v0.14.0 submariner-lighthouse-coredns registry.redhat.io/rhacm2 v0.14.0 Cluster "mbabushk-gcp" • Detecting broker(s) ... ✓ Detecting broker(s) ✓ No brokers found • Showing Connections ... ✓ Showing Connections GATEWAY CLUSTER REMOTE IP NAT CABLE DRIVER SUBNETS STATUS RTT avg. ip-10-0-94-52 mbabushk-aws 18.144.24.97 yes libreswan 172.30.0.0/16, 10.128.0.0/14 connected 21.757129ms • Showing Endpoints ... ✓ Showing Endpoints CLUSTER ENDPOINT IP PUBLIC IP CABLE DRIVER TYPE mbabushk-gcp 10.0.128.4 34.82.141.220 libreswan local mbabushk-aws 10.0.94.52 18.144.24.97 libreswan remote • Showing Gateways ... ✓ Showing Gateways NODE HA STATUS SUMMARY mbabushk-gcp-c2vpx-submariner- active All connections (1) are established • Showing Network details ... ✓ Showing Network details Discovered network details via Submariner: Network plugin: OVNKubernetes Service CIDRs: [172.31.0.0/16] Cluster CIDRs: [10.132.0.0/14] • Showing versions ... ✓ Showing versions COMPONENT REPOSITORY VERSION submariner-gateway registry.redhat.io/rhacm2 v0.14.0 submariner-routeagent registry.redhat.io/rhacm2 v0.14.0 submariner-operator registry.redhat.io/rhacm2 3fd1f0ec672e20ea2d2645d1d4510413304ade3f470cde3507bce4672a943002 submariner-lighthouse-agent registry.redhat.io/rhacm2 v0.14.0 submariner-lighthouse-coredns registry.redhat.io/rhacm2 v0.14.0
Both clusters have a gateway node created, labeled and working in "active" state.
Both clusters have "submariner" object with no errors.
Environment logs attached.
