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

TestEventingCreateEventingCluster fails on 7.1

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.3.0
    • testing
    • None

    Description

      With 7.1.0-1558 (on master branch);

      === CONT TestOperator/TestEventingCreateEventingCluster
      		 
       couchbase_util.go:802:
      		 
       util.go:1255: timeout: remote call failed with response: 400 Bad Request {
      		 
       "name": "ERR_INVALID_CONFIG",
      		 
       "code": 38,
      		 
       "description": "Invalid configuration",
      		 
       "attributes": null,
      		 
       "runtime_info": {
      		 
       "code": 38,
      		 
       "info": "functionScope bucket name should not be empty"
      		 
       }
      		 
       }

      Test works & passes fine with 7.0.2.

      This same issue seems to also be affecting TestBackupAndRestoreDisableEventing, TestBackupAndRestoreDisableEventingS3, TestEventingKillEventingPods, and TestEventingResizeCluster.

      Attachments

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

        Activity

          Ascending order - Click to sort in descending order
          roo.thorp Roo Thorp added a comment -

          I think this is happening because of changes made in MB-29224 that seem to have added extra required fields when creating an eventing function. While this doesn't affect the operator (which I don't think does anything with eventing?) it does break our eventing tests; this might mean we have to use different functions for pre and post 7.1?

          roo.thorp Roo Thorp added a comment - I think this is happening because of changes made in MB-29224 that seem to have added extra required fields when creating an eventing function. While this doesn't affect the operator (which I don't think does anything with eventing?) it does break our eventing tests; this might mean we have to use different functions for pre and post 7.1?
          roo.thorp Roo Thorp added a comment -

          Seems to have been fixed on server side.

          Broken in 7.1.0 build 1601, but looks to work fine in 1650.

          roo.thorp Roo Thorp added a comment - Seems to have been fixed on server side. Broken in 7.1.0 build 1601, but looks to work fine in 1650.

          People

            roo.thorp Roo Thorp
            roo.thorp Roo Thorp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty