[release-3.11] Bug 1930100: Pod status patches

[rphillips]

Backports two upstream fixes into 3.11 for pod statuses: 86320 and 88591.

[openshift-ci]

@rphillips: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-3.11] Pod status patches

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.

[openshift-ci]

@rphillips: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

[release-3.11] Pod status patches

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.

[nee1esh]

/retitle [release-3.11] Bug 1930100: Pod status patches

[openshift-ci]

@rphillips: This pull request references Bugzilla bug 1930100, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (3.11.z) matches configured target release for branch (3.11.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (schoudha@redhat.com), skipping review request.

In response to this:

[release-3.11] Bug 1930100: Pod status patches

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.

[nee1esh]

/retest

[brenton]

/retest

[brenton]

please forgive the noise, I'm trying configure the jobs to use a dockerhub account that won't hit the current rate limits.

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[brenton]

/retest

[nee1esh]

/retest

[openshift-ci]

@rphillips: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-gcp-crio	a365637	link	/test e2e-gcp-crio

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/test-infra repository. I understand the commands that are listed here.

[mrunalp]

/override cmd

[openshift-ci]

@mrunalp: mrunalp unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file.

In response to this:

/override cmd

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.

[mrunalp]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: mrunalp, rphillips

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

The pull request process is described 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

[sjenning]

/override cmd

[openshift-ci]

@sjenning: /override requires a failed status context to operate on.
The following unknown contexts were given:

• cmd

Only the following contexts were expected:

• ci/openshift-jenkins/cmd
• ci/openshift-jenkins/end_to_end
• ci/openshift-jenkins/extended_clusterup
• ci/openshift-jenkins/extended_conformance_install
• ci/prow/e2e-gcp
• ci/prow/e2e-gcp-crio
• ci/prow/images
• ci/prow/integration
• ci/prow/unit
• ci/prow/verify
• tide

In response to this:

/override cmd

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.

[sjenning]

/override ci/openshift-jenkins/cmd

[openshift-ci]

@sjenning: Overrode contexts on behalf of sjenning: ci/openshift-jenkins/cmd

In response to this:

/override ci/openshift-jenkins/cmd

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.

[openshift-bot]

/retest

Please review the full test history for this PR and help us cut down flakes.

[openshift-ci]

@rphillips: All pull requests linked via external trackers have merged:

• openshift/origin#26237

Bugzilla bug 1930100 has been moved to the MODIFIED state.

In response to this:

[release-3.11] Bug 1930100: Pod status patches

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.