If a rebalance is attempted and the first attempt fails, it will be retried again. Once the rebalance successfully completes, only a rebalance incomplete event is seen. It would make more sense to report rebalance complete in the scenario and only report rebalance incomplete in scenarios where all retries have been exhausted. Otherwise, tests will fail like this:
This looks like rebalanced failed, but the cluster status before the events are checked is "balanced", ""healthy", and "ready".
|For Gerrit Dashboard: K8S-543|
|98485,12||K8S-543: Add debug level log messages for HTTP requests/responses||master||gocbmgr||Status: ABANDONED||-2||+1|
|98583,6||K8S-543: Check to see if the rebalance status is stale or timed out||master||gocbmgr||Status: MERGED||+2||+1|
|98584,5||K8S-543: Remove stale status check when checking the rebalance status||master||gocbmgr||Status: MERGED||+2||+1|
|98591,2||K8S-543: Update gocbmgr to pick up rebalance status fixes||master||couchbase-operator||Status: MERGED||+2||+1|