NO-JIRA: Tolerate events during the vSphere CSI driver removal test#31124
NO-JIRA: Tolerate events during the vSphere CSI driver removal test#31124jsafrane wants to merge 2 commits intoopenshift:mainfrom
Conversation
Test "vSphere CSI Driver Operator Removal" un-installs the CSI driver + installs it back. I.e. a DaemonSet and two Deployment with many events like "Created pod: vmware-vsphere-csi-driver-node-tkl25"
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@jsafrane: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Caution Review failedFailed to post review comments WalkthroughBroadens vSphere-related E2E test detection by adding an additional test-name substring to the interval matcher and introducing a helper that checks whether an upgrade-event interval overlaps any E2E test matching a given substring; the helper is used to refine a storage-specific exception path. ChangesvSphere E2E Interval Detection and Overlap Handling
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 11 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (11 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: jsafrane The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@jsafrane: This PR was included in a payload test run from openshift/vmware-vsphere-csi-driver-operator#337
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/feb5b540-4879-11f1-9b84-0bd24eaf093f-0 |
|
Scheduling required tests: |
|
@jsafrane: This PR was included in a payload test run from openshift/vmware-vsphere-csi-driver-operator#337
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/37759370-4936-11f1-9e56-9cae5cc88990-0 |
|
@jsafrane: This PR was included in a payload test run from openshift/vmware-vsphere-csi-driver-operator#337
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/96558910-4952-11f1-97b0-fb3ae878c0e7-0 |
…test The test "vSphere CSI Driver Operator Removal should successfully remove and restore storage resources" removes the vSphere CSI driver and re-installs it back. During that test the Storage may become temporarily Available: false. When adding it back, the desired cluster configuration is that is that the driver should be available, but it takes a while to reach that state.
|
@jsafrane: This PR was included in a payload test run from openshift/vmware-vsphere-csi-driver-operator#337
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d510caf0-4968-11f1-8c7c-279887907322-0 |
|
Scheduling required tests: |
|
@jsafrane: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Test "vSphere CSI Driver Operator Removal" un-installs the CSI driver + installs it back. I.e. a DaemonSet and two Deployment are deleted + re-created with many events like "Created pod: vmware-vsphere-csi-driver-node-tkl25"
See openshift/vmware-vsphere-csi-driver-operator#337 that adds the test + a rehearsal result
Summary by CodeRabbit