-
Couldn't load subscription status.
- Fork 1.1k
server/*: Fix a bug where the GID is not added to /etc/group when run_as_group is set #8251
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
Conversation
|
Hi @PannagaRao. Thanks for your PR. I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #8251 +/- ##
==========================================
- Coverage 49.56% 49.48% -0.08%
==========================================
Files 153 153
Lines 16955 17038 +83
==========================================
+ Hits 8403 8432 +29
- Misses 7505 7544 +39
- Partials 1047 1062 +15 |
|
/ok-to-test |
|
/ok-to-test |
| } | ||
|
|
||
| if !genPasswd && !genGroup { | ||
| break |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm unsure the "break" here breaks us out of the loop and not the switch statement? we may need a goto (even though I don't like how they look)
|
I think pulling latest and rebasing this PR should fix the test failures It LGTM besides one remaining question (it wouldn't hurt to have it as-is) |
|
/retest |
|
/retest |
|
/hold Please update both the commit subject and the title of this Pull Request such that it explains what is being added. We already know that there are "changes" made here, since this is a Pull Request. |
| username = "default" | ||
| } | ||
| if homedir == "" { | ||
| homedir = "/tmp" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it would be better to set this to /nonexistent?
@cri-o/cri-o-maintainers, thoughts?
When securityContext of runAsGroup is added the gid has to be added in /etc/group. This PR has changes to add gid value under /etc/group Test case to verify the addition of the same is also being added Signed-off-by: PannagaRamamanohara <[email protected]>
|
/approve |
|
/unhold |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, kwilczynski, PannagaRao, sohankunkerkar 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 |
|
/retest |
|
/cherry-pick release-1.30 |
|
/cherry-pick release-1.29 |
|
@kwilczynski: new pull request created: #8558 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-sigs/prow repository. |
|
@kwilczynski: #8251 failed to apply on top of branch "release-1.29": 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-sigs/prow repository. |
|
OK. Will cherry-pick manually. |
When securityContext of runAsGroup is added the
gid has to be added in /etc/group. Test case for
the same is also being added
What type of PR is this?
/kind bug
What this PR does / why we need it:
This PR has changes to add gid [value of RunAsGroup in SecurityContext] under /etc/group
Which issue(s) this PR fixes:
Fixes #8216
Special notes for your reviewer:
Does this PR introduce a user-facing change?