OCPBUGS-11560,OCPBUGS-11629: flake Pods Extended Pod Container lifecycle evicted pods

[rphillips]

Flake Pods Extended Pod Container lifecycle evicted pods should be terminal test.

I had a conversation with upstream about backporting kubernetes/kubernetes#115331. 115331 depends on other changes for correctness and is also risky to backport. For now, the best we can do is flake this test and work on Clayton's upstream redesign to fix these subsystems.

[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:

OCPBUGS-11560: flake Pods Extended Pod Container lifecycle evicted pods

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-robot]

@rphillips: This pull request references Jira Issue OCPBUGS-11560, which is invalid:

• expected Jira Issue OCPBUGS-11560 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In 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.

[mrunalp]

/lgtm

[openshift-ci-robot]

@rphillips: This pull request references Jira Issue OCPBUGS-11560, which is invalid:

• expected Jira Issue OCPBUGS-11560 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Flake Pods Extended Pod Container lifecycle evicted pods should be terminal test.

I had a conversation with upstream about backporting kubernetes/kubernetes#115331. 115331 depends on other changes for correctness and is also risky to backport. For now, the best we can do is flake this test and work on Clayton's upstream redesign to fix these subsystems.

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:

OCPBUGS-11560: flake Pods Extended Pod Container lifecycle evicted pods

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-robot]

@rphillips: This pull request references Jira Issue OCPBUGS-1629, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target the "4.10.z" version, but it targets "4.12.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• expected Jira Issue OCPBUGS-1629 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Flake Pods Extended Pod Container lifecycle evicted pods should be terminal test.

I had a conversation with upstream about backporting kubernetes/kubernetes#115331. 115331 depends on other changes for correctness and is also risky to backport. For now, the best we can do is flake this test and work on Clayton's upstream redesign to fix these subsystems.

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:

OCPBUGS-11560, OCPBUGS-1629: flake Pods Extended Pod Container lifecycle evicted pods

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.

[jluhrsen]

/lgtm

[aravindhp]

/jira refresh

[openshift-ci-robot]

@aravindhp: This pull request references Jira Issue OCPBUGS-1629, which is invalid:

• expected the bug to be open, but it isn't
• expected the bug to target the "4.10.z" version, but it targets "4.12.0" instead
• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Done) instead
• expected Jira Issue OCPBUGS-1629 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[aravindhp]

/label jira/valid-bug

[aravindhp]

/remove-label jira/invalid-bug

[openshift-ci]

@aravindhp: The label(s) /remove-label jira/invalid-bug cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label jira/invalid-bug

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:

OCPBUGS-11560, OCPBUGS-16291: flake Pods Extended Pod Container lifecycle evicted pods

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.

[dcbw]

/retitle OCPBUGS-11560,OCPBUGS-11629: flake Pods Extended Pod Container lifecycle evicted pods

[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:

OCPBUGS-11560,OCPBUGS-11629: flake Pods Extended Pod Container lifecycle evicted pods

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-robot]

@rphillips: This pull request references Jira Issue OCPBUGS-11560, which is invalid:

• expected Jira Issue OCPBUGS-11560 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

This pull request references Jira Issue OCPBUGS-11629, which is invalid:

• expected the bug to target the "4.10.z" version, but no target version was set
• expected Jira Issue OCPBUGS-11629 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

Flake Pods Extended Pod Container lifecycle evicted pods should be terminal test.

I had a conversation with upstream about backporting kubernetes/kubernetes#115331. 115331 depends on other changes for correctness and is also risky to backport. For now, the best we can do is flake this test and work on Clayton's upstream redesign to fix these subsystems.

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.

[dcbw]

/jira refresh

[openshift-ci-robot]

@dcbw: This pull request references Jira Issue OCPBUGS-11560, which is invalid:

• expected Jira Issue OCPBUGS-11560 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

This pull request references Jira Issue OCPBUGS-11629, which is invalid:

• expected Jira Issue OCPBUGS-11629 to depend on a bug targeting a version in 4.11.0, 4.11.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Retaining the jira/valid-bug label as it was manually added.

In response to this:

/jira refresh

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.

[knobunc]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jluhrsen, knobunc, 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:

• test/extended/util/annotate/OWNERS [knobunc]

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

[aravindhp]

/retest-required

[openshift-ci]

@rphillips: 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/e2e-aws-single-node	f6bef15	link	false	/test e2e-aws-single-node
ci/prow/okd-e2e-gcp	f6bef15	link	false	/test okd-e2e-gcp

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.

[aravindhp]

/label cherry-pick-approved
/label backport-risk-assessed

[openshift-ci-robot]

@rphillips: Jira Issue OCPBUGS-11560: All pull requests linked via external trackers have merged:

• openshift/origin#27872

Jira Issue OCPBUGS-11560 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-11629: All pull requests linked via external trackers have merged:

• openshift/origin#27872

Jira Issue OCPBUGS-11629 has been moved to the MODIFIED state.

In response to this:

Flake Pods Extended Pod Container lifecycle evicted pods should be terminal test.

I had a conversation with upstream about backporting kubernetes/kubernetes#115331. 115331 depends on other changes for correctness and is also risky to backport. For now, the best we can do is flake this test and work on Clayton's upstream redesign to fix these subsystems.

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.