Description
With 7.1.0-1601 (on master branch);
=== CONT TestOperator/TestXDCRDeleteReplication
|
util.go:1255: timeout: document count 200, expected 100 |
INFO[0260] TestOperator/TestXDCRDeleteReplication ✗ |
Test works & passes fine with 7.0.2. This looks like the deletion of the replication K8s object is not stopping replication between the clusters.
The test successfully deletes the replication - both the K8s API object (kubectl get couchbasereplications), and the replication in the Couchbase UI disappear. The remote cluster is still listed in the UI (we just delete the Replication), but I don't think this makes a difference (the remote cluster also remains in the UI for 7.0.2, where this test passes).