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.

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

The ScaleIO volume plugin is not applying fsGroup value properly #50794

Closed
vladimirvivien opened this issue Aug 16, 2017 · 3 comments
Closed

The ScaleIO volume plugin is not applying fsGroup value properly #50794

vladimirvivien opened this issue Aug 16, 2017 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@vladimirvivien
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:
The ScaleIO volume plugin is not applying fsGroup value properly.

What you expected to happen:
When fsGroup value is specified in the spec, the mounted volume does not reflect the expected value of the fsGroup.

How to reproduce it (as minimally and precisely as possible):
Set fsGroup value in a spec:

apiVersion: v1
kind: Pod
spec:
  securityContext:
    runAsUser: 1000
    fsGroup: 2000
...

After pod is deployed, the mounted directory for the volume does not reflect the fsGroup value.

Environment:

  • Kubernetes version (use kubectl version): 1.7.x and lower
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Aug 16, 2017
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 16, 2017
@k8s-github-robot
Copy link

@vladimirvivien
There are no sig labels on this issue. Please add a sig label by:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <label>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. You can find the group list here and label list here.
The <group-suffix> in the method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals

@vladimirvivien vladimirvivien mentioned this issue Aug 16, 2017
Merged
@xiangpengzhao
Copy link
Contributor

/sig storage

@k8s-ci-robot k8s-ci-robot added the sig/storage Categorizes an issue or PR as relevant to SIG Storage. label Aug 17, 2017
@k8s-github-robot k8s-github-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 17, 2017
k8s-github-robot pushed a commit that referenced this issue Aug 22, 2017
Merge pull request #49973 from vladimirvivien/automated-cherry-pick-o…
a1e16ea 
…f-#48999-upstream-release-1.7

Automatic merge from submit-queue

ScaleIO Volume Plugin - volume attribute updates

This commit introduces the following updates and fixes:
- Enable scaleIO volume multip-mapping based on accessMode
- No longer uses "default" as default values for storagepool & protection domain
- validates capacity when capacity is zero
- Better naming for PV and volume
- make mount ro when accessModes contains ROM

**Special notes for your reviewer**:
- Related bug - #50794
- This is being cherry-picked for PR #48999

Fixes: #50794

**Release note**:
```release-note
ScaleIO: fixed enforcement of fsGroup, enabled multiple-instance volume mapping, adjusted alignment of PVC, PV, and volume names for dynamic provisioning
```
@vladimirvivien
Copy link
Member Author

This was fixed in 1.8 and backported in 1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@vladimirvivien @k8s-github-robot @xiangpengzhao @k8s-ci-robot