Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
Couchbase Server Version 7.1.0-2549
-
1
Description
Couchbase Server: 7.1.0 Rc4 build
DAC, Operator, Certification-Image: latest build.
TestCase: TestRemoveForeignNode
BackTrace:
=== CONT TestOperator/TestRemoveForeignNode
|
util.go:1390: timeout: unexpected status code: request failed POST http://test-couchbase-mvxk8.test-wpszf.svc:8091/controller/addNode 400 Bad Request: ["http is prohibited due to security reasons, please use https"] |
util.go:1391: goroutine 273 [running]: |
runtime/debug.Stack()
|
runtime/debug/stack.go:24 +0x72 |
github.com/couchbase/couchbase-operator/test/e2e/e2eutil.Die(0xc000791ba0, {0x48cfb80, 0xc00011e100}) |
github.com/couchbase/couchbase-operator/test/e2e/e2eutil/util.go:1386 +0x36 |
github.com/couchbase/couchbase-operator/test/e2e/e2eutil.MustAddNode(0xc000938ab0, 0x3c92d95, 0xc, {0xc0009e5140, 0x3, 0x4}, {0x49566d8, 0xc000475560}) |
github.com/couchbase/couchbase-operator/test/e2e/e2eutil/couchbase_util.go:483 +0x9f |
github.com/couchbase/couchbase-operator/test/e2e.TestRemoveForeignNode(0x0) |
github.com/couchbase/couchbase-operator/test/e2e/node_test.go:336 +0xc7b |
testing.tRunner(0xc000791ba0, 0x3d8a9d8) |
testing/testing.go:1259 +0x230 |
created by testing.(*T).Run
|
testing/testing.go:1306 +0x727 |
No Error in Operator Logs since the Operator is in paused state when we are trying to add the node through REST or if we try to add the node through UI which makes it operator unmanaged.
Operator Logs attached.
Upgrade test cases like:
TestUpgrade
|
TestUpgradeSupportableKillStatefulPodOnCreate,
|
TestUpgradeSupportableKillStatefulPodOnRebalance,
|
TestUpgradeSupportableKillExistingStatefulPodOnRebalance
|
works for upgrade from 6.6.4 and 7.0.3 to 7.1.0-RC4, which makes me assume that this happens only for Operator in paused state when adding 7.1.0 node to the cluster.
The upgrade from 6.6.2 to 7.1.0-RC4 works as well after upgrade from Operator 2.2.3 to Operator 2.3.0.
Additionally, We can scale-up a 7.1.0 cluster from 1 node to 2 nodes without any issue.
The error comes up when Operator is in paused state or when user tries to perform unmanaged node ops, hence I am not putting this issue as Major.