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

Openshift: Unable to login to the Couchbase UI with the AWS ELB service

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • None
    • openshift

    Description

      Issue:

      Unable to login to the Couchbase UI

      Environment:

      Openshift 3.11 integrated with AWS

      Problem:

      • Tried bringing up the couchbase cluster with the following spec (snippet):

      kind: CouchbaseCluster
      metadata:
       name: cb-example
      spec:
       tls:
       static:
       member:
       serverSecret: couchbase-server-tls
       operatorSecret: couchbase-operator-tls
       baseImage: registry.connect.redhat.com/couchbase/server
       version: 5.5.3-3
       authSecret: cb-example-auth
       exposeAdminConsole: true
       adminConsoleServiceType: LoadBalancer
       adminConsoleServices:
       - data
       exposedFeatures:
       - xdcr
       exposedFeatureServiceType: LoadBalancer

      • I was seeing the error that the cb-example-ui service was not getting assigned an ELB service:

      • When I performed a describe on the service, I found the error below that the clientIP type is not supported by ELB:

      • As per Simon's workaround, I tried adding platform as aws in the spec:

      apiVersion: couchbase.com/v1
      kind: CouchbaseCluster
      metadata:
       name: cb-example
      spec:
       tls:
       static:
       member:
       serverSecret: couchbase-server-tls
       operatorSecret: couchbase-operator-tls
       platform: aws
       baseImage: registry.connect.redhat.com/couchbase/server
       version: 5.5.3-3
       authSecret: cb-example-auth
       exposeAdminConsole: true
       adminConsoleServiceType: LoadBalancer
       adminConsoleServices:
       - data
       exposedFeatures:
       - xdcr
       exposedFeatureServiceType: LoadBalancer
       dns:
       domain: couchbase.cloud

      • Now I see the ELB getting assigned properly to the cb-example-ui svc (client affinity : none):

      • However, not able to go past the login screen even if i give the correct username and password:

       

      •  Since sessionAffinity is None, couchbase UI login is not working.

       

       

      Attachments

        1. client-ip-type-not-supported.png
          client-ip-type-not-supported.png
          544 kB
        2. elb-assigned.png
          elb-assigned.png
          190 kB
        3. login-stuck.png
          login-stuck.png
          156 kB
        4. pending-elb.png
          pending-elb.png
          191 kB
        5. session-affinity-none.png
          session-affinity-none.png
          194 kB

        Issue Links

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

          Activity

            Tommie McAfee I looked at this with Sindhura Palakodety and this is a server-side issue caused by MB-31756. Nothing for us to fix on the operator side but our thinking was to keep this (perhaps closed as "Won't Fix" or something) so that people who google for the issue can find it, also for us to include in release notes etc (cc Eric Schneider).

            matt.carabine Matt Carabine (Inactive) added a comment - Tommie McAfee I looked at this with Sindhura Palakodety and this is a server-side issue caused by MB-31756 . Nothing for us to fix on the operator side but our thinking was to keep this (perhaps closed as "Won't Fix" or something) so that people who google for the issue can find it, also for us to include in release notes etc (cc Eric Schneider ).

            Sounds good, say we close once the release note is pushed.  Eric Schneider, this is AWS/EKS specific so we will probably want a note in the cloud setup area along with Release Notes.

            Known Issues and Limitations

            Summary:  The Administrator Console cannot be exposed using a LoadBalancer service in AWS because the services backed by Elastic Load Balancing do not perform session stickiness, and a server-side issue caused by MB-31756 requires clients to remain connected to a specific node.  Therefore the Console should be exposed using a NodePort service or through a an exposed LoadBalancer service of a specific Pod. 

            tommie Tommie McAfee added a comment - Sounds good, say we close once the release note is pushed.   Eric Schneider , this is AWS/EKS specific so we will probably want a note in the cloud setup area along with Release Notes. Known Issues and Limitations Summary:   The Administrator Console cannot be exposed using a LoadBalancer service in AWS because the services backed by Elastic Load Balancing do not perform session stickiness, and a server-side issue caused by MB-31756  requires clients to remain connected to a specific node.  Therefore the Console should be exposed using a NodePort service or through a an exposed LoadBalancer service of a specific Pod. 

            Added this info to the EKS section. Longer term, I'll probably have to rethink the way cloud docs are laid out since we'll probably have to address AWS, Azure, and GCP more broadly.

            http://review.couchbase.org/#/c/107858/

            eric.schneider Eric Schneider (Inactive) added a comment - - edited Added this info to the EKS section. Longer term, I'll probably have to rethink the way cloud docs are laid out since we'll probably have to address AWS, Azure, and GCP more broadly. http://review.couchbase.org/#/c/107858/

            People

              tommie Tommie McAfee
              sindhura.palakodety Sindhura Palakodety (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty