-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Add spec.Name() to the configmap GetVolumeName() #28534
Add spec.Name() to the configmap GetVolumeName() #28534
Conversation
GCE e2e build/test failed for commit 4c17e9638ed2ab2c520d952a88864efbc3bfbd95. Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake. |
This is to base the name on the volume not just on the source configMap. If you have 2 volumes that both have the same configMap as a source, the volume is see as being in the attached state (it's state is looked up based on GetVolumeName()). See bug kubernetes#28502
4c17e96
to
d7150bf
Compare
GCE e2e build/test passed for commit d7150bf. |
cc @pmorie |
LGTM Thanks @asalkeld |
We should cherry pick this for the v1.3.1 release |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit d7150bf. |
Automatic merge from submit-queue |
@asalkeld Can you make sure to create a cherry pick for this to the 1.3 release branch. |
@asalkeld Cherrypick approved. Please create a cherrypick PR. Thanks. |
@asalkeld Ping on this. |
@saad-ali SG. Thanks for checking. |
This is to base the name on the volume not just on the
source configMap. If you have 2 volumes that both have the same
configMap as a source, the volume is see as being in the attached
state (it's state is looked up based on GetVolumeName()).
Fixes #28502