Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[release-1.17] server: cleanup container in runtime after failed creation #4206

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
openshift-cherrypick-robot wants to merge 1 commit into from
Closed

[release-1.17] server: cleanup container in runtime after failed creation #4206

openshift-cherrypick-robot wants to merge 1 commit into from

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Sep 16, 2020

This is an automated cherry-pick of #4201

/assign haircommander

Fixed a bug where a container creation failure caused that container to leak in the runtime

@haircommander
server: cleanup container in runtime after failed creation
2e55dd2 
otherwise, we leak containers in runc

Signed-off-by: Peter Hunt <[email protected]>
@openshift-ci-robot openshift-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Sep 16, 2020
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Sep 16, 2020
Merged
@saschagrunert saschagrunert changed the title [release-1.17] [1.19] server: cleanup container in runtime after failed creation [release-1.17] server: cleanup container in runtime after failed creation Sep 16, 2020
saschagrunert
saschagrunert approved these changes Sep 16, 2020
View reviewed changes
Copy link
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/retest

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 16, 2020
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 16, 2020

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, saschagrunert

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 16, 2020
@saschagrunert
Copy link
Member

saschagrunert commented Sep 16, 2020

/retest

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 16, 2020

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/images 2e55dd2 link /test images
ci/prow/e2e-aws 2e55dd2 link /test e2e-aws
ci/openshift-jenkins/critest_fedora 2e55dd2 link /test critest_fedora
ci/openshift-jenkins/e2e_features_rhel 2e55dd2 link /test e2e_features_rhel
ci/openshift-jenkins/e2e_rhel 2e55dd2 link /test e2e_rhel
ci/openshift-jenkins/critest_rhel 2e55dd2 link /test critest_rhel
ci/openshift-jenkins/integration_rhel 2e55dd2 link /test integration_rhel
ci/openshift-jenkins/integration_fedora 2e55dd2 link /test integration_fedora
ci/openshift-jenkins/e2e_fedora 2e55dd2 link /test e2e_fedora
ci/openshift-jenkins/e2e_crun 2e55dd2 link /test e2e_crun
ci/openshift-jenkins/e2e_crun_cgroupv2 2e55dd2 link /test e2e_cgroupv2
ci/openshift-jenkins/e2e_features_fedora 2e55dd2 link /test e2e_features_fedora
ci/openshift-jenkins/integration_crun_cgroupv2 2e55dd2 link /test integration_cgroupv2
ci/openshift-jenkins/integration_crun 2e55dd2 link /test integration_crun
ci/kata-jenkins 2e55dd2 link /test kata-containers
Details

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.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 16, 2020

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/images 2e55dd2 link /test images
ci/prow/e2e-aws 2e55dd2 link /test e2e-aws
ci/openshift-jenkins/critest_fedora 2e55dd2 link /test critest_fedora
ci/openshift-jenkins/e2e_features_rhel 2e55dd2 link /test e2e_features_rhel
ci/openshift-jenkins/e2e_rhel 2e55dd2 link /test e2e_rhel
ci/openshift-jenkins/critest_rhel 2e55dd2 link /test critest_rhel
ci/openshift-jenkins/integration_rhel 2e55dd2 link /test integration_rhel
ci/openshift-jenkins/integration_fedora 2e55dd2 link /test integration_fedora
ci/openshift-jenkins/e2e_fedora 2e55dd2 link /test e2e_fedora
ci/openshift-jenkins/e2e_crun 2e55dd2 link /test e2e_crun
ci/openshift-jenkins/e2e_crun_cgroupv2 2e55dd2 link /test e2e_cgroupv2
ci/openshift-jenkins/e2e_features_fedora 2e55dd2 link /test e2e_features_fedora
ci/openshift-jenkins/integration_crun_cgroupv2 2e55dd2 link /test integration_cgroupv2
ci/openshift-jenkins/integration_crun 2e55dd2 link /test integration_crun
ci/kata-jenkins 2e55dd2 link /test kata-containers

Full PR test history. Your PR dashboard.

Details

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@saschagrunert saschagrunert saschagrunert approved these changes

@mrunalp mrunalp Awaiting requested review from mrunalp mrunalp is a code owner

@runcom runcom Awaiting requested review from runcom runcom is a code owner

@nalind nalind Awaiting requested review from nalind

@sameo sameo Awaiting requested review from sameo

Assignees

@saschagrunert saschagrunert

@haircommander haircommander

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @saschagrunert @haircommander