Skip to content

Add OLM controller namespace to failure dumps - #364

Open
AlexVulaj wants to merge 1 commit into
issue-158-restarted-pod-logsfrom
issue-157-olm-controller-namespace
Open

AlexVulaj wants to merge 1 commit into
issue-158-restarted-pod-logsfrom
issue-157-olm-controller-namespace

Conversation

@AlexVulaj

@AlexVulaj AlexVulaj commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #157

Adds the OpenShift OLM controller namespace to the e2e cluster dump namespace list. On test failure, the existing dump loop will collect its pods, deployments, events, and logs along with the other diagnostic namespaces.

Note: I determined the namespace from the OLM-enabled e2e workflow: it runs against OpenShift with OLM tests enabled. OpenShift runs the OLM controller components in openshift-operator-lifecycle-manager, so I added that namespace to the failure dump list.

Stacked on #360. After #360 merges, retarget this PR to main.

Validation:

  • go test ./...
  • go vet -tags=e2e ./tests/e2e

@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 1

  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review

@AlexVulaj AlexVulaj self-assigned this Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant