Kubernetes version (use kubectl version
):
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"08e099554f3c31f6e6f07b448ab3ed78d0520507", GitTreeState:"clean", BuildDate:"2017-01-12T04:52:34Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Environment:
Linux 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
What happened:
When a key doesn't exist in a configmap, it produces an error:
references non-existent config key
Adding the missing key would help with debugging.
What you expected to happen:
It should show the key
How to reproduce it (as minimally and precisely as possible):
Reference a key in a configmap that doesn't exist.
Anything else we need to know:
@ttripp There are no sig labels on this issue. Please add a sig label by:
(1) mentioning a sig: @kubernetes/sig-<team-name>-misc
(2) specifying the label manually: /sig <label>
_Note: method (1) will trigger a notification to the team. You can find the team list here._
/sig node
H,
Not sure if this is the right place to ask. But not able to understand how to resolve the error.
MountVolume.SetUp failed for volume "kubernetes.io/configmap/b690cfd1-7386-11e7-b005-080027f96241-config" (spec.Name: "config") pod "b690cfd1-7386-11e7-b005-080027f96241" (UID: "b690cfd1-7386-11e7-b005-080027f96241") with: references non-existent config key.
Most helpful comment
H,
Not sure if this is the right place to ask. But not able to understand how to resolve the error.
MountVolume.SetUp failed for volume "kubernetes.io/configmap/b690cfd1-7386-11e7-b005-080027f96241-config" (spec.Name: "config") pod "b690cfd1-7386-11e7-b005-080027f96241" (UID: "b690cfd1-7386-11e7-b005-080027f96241") with: references non-existent config key.