Skip to content
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.

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

Ensure sig-proxy default is propagated in start #6931

Merged
merged 1 commit into from
Jul 14, 2020

Conversation

mheon
Copy link
Member

@mheon mheon commented Jul 10, 2020

We properly determined what sig-proxy should be set to, but we never passed that along to the backend. As such, cases where the
default swapped (mostly when --attach was specified but the --sig-proxy flag was not) were not handled correctly

Fixes #6928

We properly determined what sig-proxy should be set to, but we
never passed that along to the backend. As such, cases where the
default swapped (mostly when `--attach` was specified but the
`--sig-proxy` flag was not) were not handled correctly

Fixes containers#6928

Signed-off-by: Matthew Heon <[email protected]>
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mheon

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:

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 Jul 10, 2020
@rhatdan
Copy link
Member

rhatdan commented Jul 11, 2020

Copy link
Member

@vrothberg vrothberg left a comment

Choose a reason for hiding this comment

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

Code LGTM but I'd love a test for that. The linked issue seems to have a reproducer that we could reuse. A system test could be especially helpful for backporting it to the v2.0 branch.

@mheon
Copy link
Member Author

mheon commented Jul 14, 2020

The existing reproducer is going to be very racy. Our eventual solution to this lives in run_signal_test.go and it's truly horrifying.

@rhatdan
Copy link
Member

rhatdan commented Jul 14, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 14, 2020
@openshift-merge-robot openshift-merge-robot merged commit a9a751f into containers:master Jul 14, 2020
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

--sig-proxy does not default to true when using -a, despite the docs
5 participants