Skip to content

failure analysis: mistaken resource apply diff for as root cause of e2e failure. #2056

Open

Description

@kaovilai

A case might fail on like

  [FAILED] Unexpected error:
      <*errors.StatusError | 0xc00101e640>: 
      container "todolist" in pod "todolist-755b6749cf-vnt2h" is waiting to start: PodInitializing
      {
          ErrStatus: {
              TypeMeta: {Kind: "", APIVersion: ""},
              ListMeta: {
                  SelfLink: "",
                  ResourceVersion: "",
                  Continue: "",
                  RemainingItemCount: nil,
              },
              Status: "Failure",
              Message: "container \"todolist\" in pod \"todolist-755b6749cf-vnt2h\" is waiting to start: PodInitializing",
              Reason: "BadRequest",
              Details: nil,
              Code: 400,
          },
      }
  occurred
  In [AfterEach] at: /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:387 @ 01/13/26 17:32:29.682
  < Exit [AfterEach] Backup and restore tests - /go/src/github.com/openshift/oadp-operator/tests/e2e/backup_restore_suite_test.go:422 @ 01/13/26 17:32:29.682 (1.391s)

but analysis got hung up on diff

## 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
```

Activity

  1. openshift-bot commented on Apr 15, 2026

    @openshift-bot

    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

  2. added
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 15, 2026
  3. self-assigned this
    on Apr 15, 2026
  4. kaovilai commented on Apr 15, 2026

    @kaovilai
    MemberAuthor

    /lifecycle froze

  5. kaovilai commented on Apr 15, 2026

    @kaovilai
    MemberAuthor

    /lifecycle frozen

  6. added
    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.
    and removed
    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.
    on Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions