Skip to content

CBQE-1857:: Add Set up Script - #1

Open
paragagarwal wants to merge 1 commit into
couchbase:masterfrom
paragagarwal:patch-1
Open

CBQE-1857:: Add Set up Script#1
paragagarwal wants to merge 1 commit into
couchbase:masterfrom
paragagarwal:patch-1

Conversation

@paragagarwal

Copy link
Copy Markdown
Contributor

This can be used for Offline and Online Upgrade

This can be used for Offline and Online Upgrade
jdmuntacb added a commit to jdmuntacb/testrunner that referenced this pull request Aug 24, 2019
…checking the fixed expected results. Girish and I had debugged this.There are lot of differences in the random.py from Python2 vs. Python3 and it looks like not possible to match exact to 2.7. I think we have 2 options. 1) Change the test case design not to rely on the random data load with fixed expected from randomness. Or 2) Update the conf files with Py3 results. For now, I am going to update couchbase#2. Later Girish can think of couchbase#1.
ns-codereview pushed a commit that referenced this pull request Sep 6, 2026
Automates the XDCR half of the MB-72047 CRL P0 test plan as a testrunner
suite, verified against 8.5.0-1077-enterprise on a 4-node fleet in a
2 + 2 topology.

  pytests/xdcr/crlXDCR.py          XDCRCRLBase + 15 tests in two classes
  pytests/xdcr/crl_xdcr_utils.py   internal-client-cert install, CA install,
                                   rotation-safe goxdcr.log counting, pid read
  conf/xdcr/py-xdcr-crl.conf       suite definition

Runs on the standard b/resources/4-nodes-template-2clusters-2nodes.ini.
The 2 + 2 shape is required, not incidental: a single-node source cluster
has no P2P peer, so surface #1 cannot fail and every local-revocation test
would pass while asserting nothing.

Two additive changes to shared helpers, both backward compatible and
neither with an existing caller outside this suite:

  crl_utils.generate_leaf_cert(email_sans=)   emits an rfc822 SAN, which is
      what makes a certificate an internal client cert -- the identity XDCR
      presents on its intra-cluster surfaces, evaluated under the nodeToNode
      CRL scope rather than clientAuth
  RestConnection.reload_client_certificate()  POST /node/controller/
      reloadClientCertificate, required by R4 and absent from the repo

Results on 8.5.0-1077, one sequential run per class:

  XDCRCRLLocalTests    9/9 pass   errors=0 failures=0 tests=9 skip=0
  XDCRCRLRemoteTests   3/6 pass

The three remote failures are the designed outcome, not a regression.
test_remote_ref_validate_revoked_cert, test_create_remote_ref_with_revoked_cert
and test_edit_remote_ref_to_revoked_cert assert the R2.1 hint text that
MB-73451 records as absent, and are marked GROUP=P2. They must go green by
that defect being fixed, never by editing the assertion. A run in which one
of them reports errors=1 rather than a hint-text assertion failure did not
reach its assertion and is not evidence about MB-73451.

Related defects confirmed still present on 8.5.0-1077, both originally filed
against 8.1.0-2594:

  MB-73451  remote-reference create/validate returns no revocation hint
  MB-73452  the auto-pause path does not surface the reason, and the blocking
            dial sites log no "possible certificate revocation" phrase. The
            second half is why the remote tests assert on the replication
            error list rather than on goxdcr.log.

The design notes, the 8.5 re-validation record and the QE handoff are kept
outside this repo and shared separately, so this change carries test code
only.

Change-Id: I1e04542fd4daef7f5b0b10eea6d4da6e3a7628f8
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Reviewed-on: https://review.couchbase.org/c/testrunner/+/252332
Tested-by: Ayush Nayyar <ayush.nayyar@couchbase.com>
Reviewed-by: <dananjay.s@couchbase.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant