You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLOUDP-302662: Disable cluster level telemetry on Openshift e2e (#4127)
# Summary
Openshift e2e tests run on a static cluster. When running multiple tests
in parallel or when a test has not been cleaned up, the installation of
the operator fails when installing cluster roles since they need to be
owned by a specific helm release.
Sample error log:
https://evergreen.mongodb.com/rest/v2/tasks/ops_manager_kubernetes_e2e_mdb_openshift_ubi_cloudqa_e2e_crd_validation_d9302abbec0e04333374b22e159fafce720d1f8b_25_02_25_10_03_37/build/TestLogs/770c8557b5948815e5c422e80d89d1e0?execution=4&print_time=true
## Proof of Work
EVG patch with changes:
https://spruce.mongodb.com/version/67bedad29518090007d220a2
## Checklist
- [x] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you checked for release_note changes?
## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](REDACTED)
- Remember the following Communication Standards - use comment prefixes
for clarity:
* **blocking**: Must be addressed before approval.
* **follow-up**: Can be addressed in a later PR or ticket.
* **q**: Clarifying question.
* **nit**: Non-blocking suggestions.
* **note**: Side-note, non-actionable. Example: Praise
* --> no prefix is considered a question
0 commit comments