Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-4506

[Submariner] - 0.13.4 fails to resolve external ip

XMLWordPrintable

    • False
    • None
    • False
    • No

      Description of problem:

      ACM 2.6.5 / Submariner 0.13.4

      Three managed clusters:
      aws (ocp 4.12)
      gcp (ocp 4.11)
      azure (ocp 4.12)

      After deployment of submariner, all three clusters are in connection state - error.

          message: |-
            The connection between clusters "mbabushk-gcp" and "mbabushk-aws" is not established (status=error)
            The connection between clusters "mbabushk-gcp" and "mbabushk-azure" is not established (status=error) 

      It happens as gateway pod unable to retrieve external ip from the external service - my-ip.io and seeip.org

       

      The error trace is similar on all gateway pods:

      I0323 10:17:18.259165       1 response_handle.go:32] Received response from 40.122.237.250:4490 - REQUEST_NUMBER: 0x764d3f28bf259eb6, RESPONSE: NAT_DETECTED, SENDER: "submariner-cable-mbabushk-azure-10-0-186-0", RECEIVER: "submariner-cable-mbabushk-aws-10-0-55-248"
      I0323 10:17:18.259192       1 remote_endpoint.go:165] selected public IP "40.122.237.250" for endpoint "submariner-cable-mbabushk-azure-10-0-186-0"
      E0323 10:19:47.378828       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      E0323 10:20:48.274294       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      I0323 10:21:11.391190       1 node_handler.go:66] areNodesEquivalent called for "ip-10-0-55-248.us-east-2.compute.internal", existingGlobalIP "242.2.255.254", newGlobalIP "242.2.255.254"
      E0323 10:22:10.576719       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      E0323 10:23:11.701215       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      E0323 10:24:13.700697       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      E0323 10:24:13.817400       1 public_ip.go:81] Error resolving public IP with resolver api:ip4.seeip.org : retrieving public IP from https://ip4.seeip.org: Get "https://ip4.seeip.org": EOF
      E0323 10:25:15.381527       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      E0323 10:25:15.512026       1 public_ip.go:81] Error resolving public IP with resolver api:ip4.seeip.org : retrieving public IP from https://ip4.seeip.org: Get "https://ip4.seeip.org": EOF
      E0323 10:26:17.101701       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
      I0323 10:26:17.890343       1 node_handler.go:66] areNodesEquivalent called for "ip-10-0-55-248.us-east-2.compute.internal", existingGlobalIP "242.2.255.254", newGlobalIP "242.2.255.254"
      E0323 10:27:17.764728       1 public_ip.go:81] Error resolving public IP with resolver api:api.my-ip.io/ip : No IPv4 found in: "<html>\r\n<head><title>429 Too Many Requests</title></head>\r\n<body>\r\n<center><h1>429 Too Many Requests</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
       

      Environment logs attached.

       

      40 minutes after deployment, the gateway pods still unable to query the external ip.

              sgaddam@redhat.com Gaddam Sridhar
              mbabushk@redhat.com Maxim Babushkin
              Maxim Babushkin Maxim Babushkin
              ACM QE Team
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: