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
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
openshift-cibot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Apr 29, 2024
Today, azure and gcp create non default secrets and do not add that info to SnapshotLocations in DPA, but nevertheless, this test do not break
oadp-operator/tests/e2e/dpa_deployment_suite_test.go
Line 412 in a663e78
We should validate BSL/VSL in our tests
For consistency, SnapshotLocations build code should be updated to have similar logic to BackupLocations one
oadp-operator/tests/e2e/lib/dpa_helpers.go
Line 82 in a663e78
oadp-operator/tests/e2e/lib/dpa_helpers.go
Lines 89 to 94 in a663e78
Also, this option should be removed also for consistency, as developer can not select BSL secret name for e2e run
oadp-operator/tests/e2e/e2e_suite_test.go
Line 33 in a663e78
The text was updated successfully, but these errors were encountered: