Details
-
Bug
-
Resolution: Fixed
-
Test Blocker
-
2.3.0-beta
-
None
-
1
Description
Operator: registry.gitlab.com/cb-vanilla/operator:latest (2.3.0-164)
Server: couchbase/server:7.0.1
Istio: STRICT
TestCase: TestBackupFullIncremental
Backup Image: registry.gitlab.com/cb-vanilla/operator-backup:1.2.0-105
Back Trace:
06:21:04 === CONT TestOperator/TestBackupFullIncremental |
06:21:04 util.go:1252: timeout: Get "http://test-couchbase-q2j8f.test-ggbg8.svc:8091/pools/default": read tcp 10.72.2.3:55666->10.72.0.5:8091: read: connection reset by peer |
06:21:04 util.go:1253: goroutine 578 [running]: |
06:21:04 runtime/debug.Stack(0x2fd8ade, 0x494d4f8, 0x30085c0) |
06:21:04 runtime/debug/stack.go:24 +0xab |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/e2eutil.Die(0xc000d44900, 0x4909800, 0xc000be07c0) |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/e2eutil/util.go:1248 +0x34 |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/e2eutil.MustWaitUntilBucketExists(0xc000d44900, 0xc0009a40e0, 0xc000d98000, 0x3d17320, 0xc000c1c1a0, 0x1bf08eb000) |
06:21:04 time="2021-10-04T13:21:01Z" level=info msg="TestOperator/TestBackupFullIncremental ✗" |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/e2eutil/wait_util.go:543 +0xfe |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e.testFullIncremental(0xc000d44900, 0xc00085ae00) |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/backup_test.go:241 +0x9d5 |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e.TestBackupFullIncremental(0xc000d44900) |
06:21:04 github.com/couchbase/couchbase-operator/test/e2e/backup_test.go:271 +0x3e |
06:21:04 testing.tRunner(0xc000d44900, 0x3e3d970) |
06:21:04 testing/testing.go:1193 +0x203 |
06:21:04 created by testing.(*T).Run |
06:21:04 testing/testing.go:1238 +0x5d8 |
Error:
Jenkins Job: http://qa.sc.couchbase.com/view/Cloud/job/k8s-cbop-gke-pipeline/380/console
As seen in the Jenkins Job mentioned above , a lot of Sanity test cases are failing with latest build of Operator and Certification with ISTIO STRICT, issue created for backup test.
I believe there's single point of failure for all test cases while waiting for bucket to come up.
Another interesting thing is after 3-4 test cases failed , the job is exiting on its own without trying to run remaining sanity test cases and no logs are collected.
(Marking it as TestBlocker , since we cannot run test cases with Istio)