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

Put the non-existent key into the error message #41573

Closed
ttripp opened this issue Feb 16, 2017 · 3 comments · Fixed by #47417
Closed

Put the non-existent key into the error message #41573

ttripp opened this issue Feb 16, 2017 · 3 comments · Fixed by #47417
Labels
sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@ttripp
Copy link

ttripp commented Feb 16, 2017

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 ttripp mentioned this issue Feb 16, 2017
Closed
@k8s-github-robot k8s-github-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 31, 2017
@k8s-github-robot
Copy link

@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.

@xilabao xilabao mentioned this issue Jun 13, 2017
Merged
@0xmichalis
Copy link
Contributor

/sig node

@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Jun 20, 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 Jun 20, 2017
rohitagarwal003 pushed a commit to rohitagarwal003/kubernetes that referenced this issue Jul 16, 2017
Merge pull request kubernetes#47417 from xilabao/print-non-existent-key
1cbb7b1 
Automatic merge from submit-queue (batch tested with PRs 47417, 47638, 46930)

print non-existent key in configmap

**What this PR does / why we need it**:

**Which issue this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes kubernetes#41573

**Special notes for your reviewer**:
carry from kubernetes#41574
**Release note**:

```release-note
NONE
```
@tusharbanne
Copy link

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.

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

Successfully merging a pull request may close this issue.

print non-existent key in configmap xilabao/kubernetes
5 participants
@0xmichalis @ttripp @tusharbanne @k8s-github-robot @k8s-ci-robot