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

Multiple mount points default-token-* #25489

Closed
daniel-yavorovich opened this issue May 11, 2016 · 6 comments
Closed

Multiple mount points default-token-* #25489

daniel-yavorovich opened this issue May 11, 2016 · 6 comments
Assignees
@matchstick
Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Milestone
next-candidate

Comments

@daniel-yavorovich
Copy link

Dear Sirs/Madams,

I use Kubernetes v1.2.4, like Docker Multinode on Ubuntu 14.04 x86_64. After installation appears multiple mount points, which increase to infinity:

# mount
...
tmpfs on /var/lib/kubelet/pods/8f23c93a-17ab-11e6-92f3-002421ef2f79/volumes/kubernetes.io~secret/default-token-9bw9j type tmpfs (rw)
tmpfs on /var/lib/kubelet/pods/74fbdeb9-17aa-11e6-92f3-002421ef2f79/volumes/kubernetes.io~secret/default-token-9i2dw type tmpfs (rw)

# mount | grep -c default-token
19934

The same situation is also manifested in the Kubernetes v1.3-alpha-1,2.

What could be the reason?
@saad-ali saad-ali added sig/storage Categorizes an issue or PR as relevant to SIG Storage. team/cluster labels May 13, 2016
@jason-kane
Copy link

same symptom here with kubernetes 1.2.1 -- mostly dupes:

~# df -h | grep tmpfs | wc -l
30438

~# df -h | grep tmpfs | sort | uniq | wc -l
65

@daniel-yavorovich
Copy link
Author

any updates?

@jason-kane jason-kane mentioned this issue Jun 6, 2016
Closed
@matchstick
Copy link
Contributor

@kubernetes/sig-storage Can you try this again with 1.3? We made some fixes in this area recently. Also please let us know more of your setup? Are you using any attached volumes? Or is this just getting the container runtimes to work?

@matchstick matchstick self-assigned this Jul 7, 2016
@jingxu97
Copy link
Contributor

jingxu97 commented Jul 7, 2016

The fix in PR #27054 might fix your issue. Please let us know if you still experience the issue. Thanks!

@saad-ali saad-ali mentioned this issue Jul 13, 2016
Closed
@childsb childsb added this to the next-candidate milestone Jul 15, 2016
@pmorie
Copy link
Member

pmorie commented Jul 25, 2016

@daniel-yavorovich is this still an issue?

@matchstick
Copy link
Contributor

Closing as we believe we have fixed this in 1.3.4. Please reopen if you can reproduce it.

@baldeynz baldeynz mentioned this issue Aug 23, 2016
Closed
openshift-publish-robot pushed a commit to openshift/kubernetes that referenced this issue Oct 1, 2020
@k8s-publishing-bot
Merge pull request kubernetes#25489 from p0lyn0mial/release-4-5-refle…
8d4bc15 
…ctor-too-large

Bug 1877346: KubeAPIErrorsHigh firing due to too large resource version

Origin-commit: 917c7c3382dea364371c411901d3655e808fe8a3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@matchstick matchstick

Labels
sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Milestone
next-candidate
Development

No branches or pull requests
7 participants
@pmorie @childsb @daniel-yavorovich @jason-kane @saad-ali @jingxu97 @matchstick