DO NOT MERGE: Output pod.status when it regresses from running to pending #25978
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
pkg/monitor/pod.go
Outdated
| conditions = append(conditions, Condition{ | ||
| Level: Warning, | ||
| Locator: locatePod(pod), | ||
| Message: fmt.Sprintf("pod moved back to Pending: old status: %s", string(debugPod)), |
There was a problem hiding this comment.
This might be a little verbose but honestly I think it might not be the worst to merge this in and see if we find anything weird/unexpected? We should be able to glean any other info we need from the must-gather.
There was a problem hiding this comment.
I was actually opening this to get data from the jobs, not to merge. Very likely to reproduce within 1-2 retests.
smarterclayton
force-pushed
the
print_fail
branch
from
1672520 to
5fcda2f
Compare
openshift-ci-robot
added
the
needs-rebase
|
@smarterclayton: PR needs rebase. DetailsInstructions 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/test-infra repository. |
|
@smarterclayton: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
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/test-infra repository. |
4 participants
No description provided.