Details
-
Bug
-
Resolution: Duplicate
-
Critical
-
Cheshire-Cat
-
1
-
CX Sprint 247
Description
Seeing this intermittent error on server-add recently, quite frequently but intermittent. Is this a known / expected issue, and should we just try to add retry logic for these? If so, should the CLI suggest the same?
2021-05-13T14:10:30.342-07:00 INFO ClusterIntegrationIT [main] Running cli: server-add -c 172.18.0.3:9000 -u couchbase -p couchbase --server-add http://172.18.0.3:9001 --server-add-username couchbase --server-add-password couchbase --services analytics
|
2021-05-13T14:10:31.695-07:00 INFO ClusterIntegrationIT [main+] >> ERROR: Prepare join failed. Got HTTP status 500 from REST call post to http://172.18.0.3:9001/engageCluster2. Body was: "[\"Unexpected server error, request logged.\"]"
|
2021-05-13T14:10:31.714-07:00 INFO CbCollectInfoTestRule [main] taking cbcollect_infos for ensureShutdownLogs(com.couchbase.analytics.test.cbserver.ClusterIntegrationIT) due to java.lang.AssertionError: couchbase-cli exit code mismatch (expected: 0 was: 1); output:
|
ERROR: Prepare join failed. Got HTTP status 500 from REST call post to http://172.18.0.3:9001/engageCluster2. Body was: "[\"Unexpected server error, request logged.\"]" expected:<0> but was:<1>
|
Attachments
Issue Links
- duplicates
-
MB-45289 [System Test] engageCluster2 POST returns status 500 - Avoid node rename
- Closed