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

cbopinfo: Services/endpoint data missing during log collection

    XMLWordPrintable

Details

    Description

      Ashwins-MacBook-Pro:couchbase-operator]$ kubectl get services --kubeconfig ~/.kube/config_BasicCluster --namespace default
      NAME                          TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
      example-etcd-cluster          ClusterIP   None            <none>        2379/TCP,2380/TCP   20m
      example-etcd-cluster-client   ClusterIP   10.107.129.60   <none>        2379/TCP            20m
      kubernetes                    ClusterIP   10.96.0.1       <none>        443/TCP             48m

      Attachments

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

        Activity

          Simon Murray there was no such prints during the execution.

          This was the testcase being executed -> TestLogCollectUsingClusterNameAndNamespace

          ashwin.govindarajulu Ashwin Govindarajulu added a comment - Simon Murray there was no such prints during the execution. This was the testcase being executed -> TestLogCollectUsingClusterNameAndNamespace
          simon.murray Simon Murray added a comment -

          I'm getting.

                  supportability_test.go:586: Collecting logs from single cluster
                  supportability_test.go:590: Returned: Wrote cluster information to cbopinfo-20180813T143001+0100.tar.gz
                  validation_test.go:59: Failure 1: File cbopinfo-20180813T143001+0100/default/endpoints/couchbase-operator/couchbase-operator.yaml
                       Error: not found
                  validation_test.go:59: Failure 2: File cbopinfo-20180813T143001+0100/default/endpoints/kubernetes/kubernetes.yaml
                       Error: not found
                  validation_test.go:59: Failure 3: File cbopinfo-20180813T143001+0100/default/service/kubernetes/kubernetes.yaml
                       Error: not found

          Which is covered by the fact that these are filtered out based on which cluster they belong to.  Will set up a name space with the correct RBAC and see if that's causing issues.

          simon.murray Simon Murray added a comment - I'm getting.         supportability_test.go:586: Collecting logs from single cluster         supportability_test.go:590: Returned: Wrote cluster information to cbopinfo-20180813T143001+0100.tar.gz         validation_test.go:59: Failure 1: File cbopinfo-20180813T143001+0100/default/endpoints/couchbase-operator/couchbase-operator.yaml              Error: not found         validation_test.go:59: Failure 2: File cbopinfo-20180813T143001+0100/default/endpoints/kubernetes/kubernetes.yaml              Error: not found         validation_test.go:59: Failure 3: File cbopinfo-20180813T143001+0100/default/service/kubernetes/kubernetes.yaml              Error: not found Which is covered by the fact that these are filtered out based on which cluster they belong to.  Will set up a name space with the correct RBAC and see if that's causing issues.
          simon.murray Simon Murray added a comment -

          Same behaviour running with a "couchbase-operator" service account in the "simon" name space.  I'm unable to recreate.  You'll have to supply exact details of how your cluster is configured.  If you can recreate the error in minikube that would be fabulous

          simon.murray Simon Murray added a comment - Same behaviour running with a "couchbase-operator" service account in the "simon" name space.  I'm unable to recreate.  You'll have to supply exact details of how your cluster is configured.  If you can recreate the error in minikube that would be fabulous

          Okay Simon Murray. I will try to reproduce it by tomorrow in my local Minikube and share the details with you.

          ashwin.govindarajulu Ashwin Govindarajulu added a comment - Okay Simon Murray . I will try to reproduce it by tomorrow in my local Minikube and share the details with you.

          Fixed the testcase according to the issue.

          Hence closing this ticket

          ashwin.govindarajulu Ashwin Govindarajulu added a comment - Fixed the testcase according to the issue. Hence closing this ticket

          People

            ashwin.govindarajulu Ashwin Govindarajulu
            ashwin.govindarajulu Ashwin Govindarajulu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty