Details
-
Bug
-
Resolution: Fixed
-
Major
-
Elixir
-
Untriaged
-
0
-
Unknown
Description
Adding nodes to a cluster_run cluster started failing recently.
e.g.
clusterrun.go:128: starting 'cluster_run' [/home/couchbase/jenkins/workspace/regulator-sanity-test/ns_server/cluster_run --serverless --nodes 3], output redirected to /home/couchbase/jenkins/workspace/regulator-sanity-test/ns_server/logs/cluster_run.out
|
clusterrun.go:156: waiting for all nodes to be ready for init
|
testutils.go:436: http://localhost:9000 reports ready (status 200)
|
testutils.go:436: http://localhost:9001 reports ready (status 200)
|
testutils.go:436: http://localhost:9002 reports ready (status 200)
|
clusterrun.go:158: all nodes report ready for init
|
clusterrun.go:301: calling 'cluster-init'
|
clusterrun.go:734: Running './couchbase-cli cluster-init --cluster-username couchbase --cluster-password couchbase -c 127.0.0.1:9000 --ip-family ipv4 --services data,index,query,fts'
|
SUCCESS: Cluster initialized
|
clusterrun.go:734: Running './couchbase-cli node-init -c 127.0.0.1:9001 -u couchbase -p couchbase --ipv4'
|
SUCCESS: Node initialized
|
clusterrun.go:734: Running './couchbase-cli server-add --no-ssl-verify -c https://127.0.0.1:19000 -u couchbase -p couchbase --server-add 127.0.0.1:19001 --server-add-username couchbase --server-add-password couchbase --services data,index,query,fts'
|
ERROR: Unable to validate certificate on host: 172.17.0.2. Please make sure the certificate on this host contains host name '172.17.0.2' in Subject Alternative Name. Refer to Couchbase docs for more info on how to create node certificates
|
Attachments
Issue Links
- is duplicated by
-
MB-55232 FTS rebalance fails on "bad certificate" in cluster_run (SERVERLESS mode ONLY)
-
- Closed
-