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
{{ message }}
Repository navigation
failure analysis: mistaken resource apply diff for as root cause of e2e failure. #2056
## Failed Tests Analysis
### 1. Mongo application DATAMOVER [CRITICAL]
**Root Cause**: SecurityContextConstraints (SCC) resource comparison failure after restore - the `allowedVolumes` field was restored with wildcard `["*"]` instead of the original detailed list of volume types.
**Evidence**:
```
junit_report.xml: "[FAILED] No known FLAKE found in a previous run, marking test as failed. In [It] at: /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:456"
Test system-err shows comparison failure:
[]any{
- string("awsElasticBlockStore"),
+ string("*"),
- string("azureDisk"),
- string("azureFile"),
- string("cephFS"),
- string("cinder"),
- string("configMap"),
- string("csi"),
- string("downwardAPI"),
... [full list of ~30 volume types replaced with "*"]
}
must-gather: Restore mongo-datamover-e2e-e0e6ccb2-f0a3-11f0-a143-0a580a828d79 shows "Phase: Completed" but SCC comparison in test failed
```
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.
Activity
openshift-bot commentedon Apr 15, 2026
Issues go stale after 90d of inactivity.
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./lifecycle stale
kaovilai commentedon Apr 15, 2026
/lifecycle froze
kaovilai commentedon Apr 15, 2026
/lifecycle frozen