Investigation for PruningCronjob Error [In Testing]

[aliceh]

In this PR I add an investigation for https://github.com/openshift/ops-sop/blob/master/v4/alerts/PruningCronjobErrorSRE.md

[aliceh]

/hold

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aliceh Once this PR has been reviewed and has the lgtm label, please assign makdaam for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci[bot]]

@aliceh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/coverage	4edb3303977754232699d811bb6a01f50b2b6d9b	link	true	/test coverage
ci/prow/test	4edb3303977754232699d811bb6a01f50b2b6d9b	link	true	/test test
ci/prow/lint	4edb3303977754232699d811bb6a01f50b2b6d9b	link	true	/test lint

Full PR test history. Your PR dashboard.

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

[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