Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-2464

[Istio] Local cluster unable to connect to remote for creating XDCR.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0
    • None
    • None
    • 42: GA items and Connect, 44: Completion 2.3, 46: Completion 2.3. bk maint
    • 1

    Description

      Server: couchbase/server:7.0.1

      Operator and Certification latest image

      Istio: Strict.

      TestCase: TestXDCRCreateCluster

      Operator Logs error:

      {"level":"info","ts":1634048298.3580697,"logger":"cluster","msg":"Reconciliation failed","cluster":"test-f4nw5/test-couchbase-dfdkh","error":"unexpected status code: request failed POST http://test-couchbase-dfdkh-0002.test-couchbase-dfdkh.test-f4nw5.svc:8091/pools/default/remoteClusters 400 Bad Request: {\"_\":\"Could not connect to \\\"10.16.0.2\\\" on port 31670. This could be due to an incorrect host/port combination or a firewall in place between the servers.\"}" 

      cbopinfo attached.

      Note: The remote scenarios of XDCR pass with Istio Strict.

      The failure might be related to testing or more specifically with how we use the GenericNetworking method to create remote cluster and not to Operator directly.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            simon.murray Simon Murray added a comment -

            No it's because IBM and Cisco, both powerhouses in the networking space, say it's unsafe and stupid.

            simon.murray Simon Murray added a comment - No it's because IBM and Cisco, both powerhouses in the networking space, say it's unsafe and stupid.

            Read this... generic networking is terrible, we should be dropping it entirely https://docs.google.com/document/d/1UWUVXG_IqB17Pl2OB0JCLXENFdX26swJ77QtCFNxXNg/edit

            simon.murray Simon Murray added a comment - Read this... generic networking is terrible, we should be dropping it entirely https://docs.google.com/document/d/1UWUVXG_IqB17Pl2OB0JCLXENFdX26swJ77QtCFNxXNg/edit

            ok, Thanks Simon Murray , thanks for sharing this.

            roshani.sanghavi Roshani Sanghavi (Inactive) added a comment - ok, Thanks Simon Murray  , thanks for sharing this.

            I propose we skip the tests and then with the docs change we've completed what we will do to "fix" this. Separately we probably need to formally deprecate GenericNetworking, I think we've done all we can to make it visible other than that.

            patrick.stephens Patrick Stephens (Inactive) added a comment - I propose we skip the tests and then with the docs change we've completed what we will do to "fix" this. Separately we probably need to formally deprecate GenericNetworking, I think we've done all we can to make it visible other than that.

            Closing this as per last comment - pls reopen if anything is pending

            arunkumar Arunkumar Senthilnathan (Inactive) added a comment - Closing this as per last comment - pls reopen if anything is pending

            People

              prateek.kumar Prateek Kumar (Inactive)
              prateek.kumar Prateek Kumar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty