-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
A lot of house-keeping messages in logs #1490
Comments
@smarterclayton @deads2k any clues? |
fyi, I'm running up-to-date f21 box in vagrant.... these messages started to appear last week, so I assume something in k8s changed and it is touching things it should not touch... |
another weirdness is that right now my 'docker ps' command get stuck... no output, just hangs... |
I'm seeing those messages as well (I'm using f21 vbox vagrant) whenever starting a pod (either through builds or deployments). But once pods are all started up the logs are gone. Additionally I can still run any command eg. |
In libvirt I can see only 'pod' container running, any other container is ran and then stopped and restarted... There is nothing in logs... |
These are from cAdvisor, you'll want to engage Victor or Vish upstream about it. |
@smarterclayton can we make them more silent? ;-) |
It came in with the last rebase. Kube had it for a while, but our kubelet start up has drifted from upstream. |
I believe some of these have been squelched by my pull to cAdvisor last week. |
@smarterclayton what is interesting is that this message cause the openshift to hang:
(there is no log output after this point) The osc:
|
What does CTRL+\ tell you?
|
@smarterclayton I killed it :-( but next time I will provide that output |
These have all been muted. |
…service-catalog/' changes from 892b0368f0..3064247d05 3064247d05 origin build: add origin tooling 48ecff1 Chart changes for 0.1.2 (openshift#1527) 8727247 Fix change validator to look up serviceclass properly (openshift#1518) b0b138b Broker Reconciliation occurs too frequently (openshift#1514) cc816eb When a SI is unbindable, mark the binding request failed. (openshift#1522) 41290e9 Clarify semantics around RelistDuration (openshift#1516) 6bcb593 Send Context with UpdateInstanceRequest (openshift#1517) c3b72d8 Enforce stricly increasing broker relistRequests (openshift#1515) 01d81e5 Follow up from openshift#1450 and openshift#1444 (openshift#1504) 5e77882 Retry failed deprovision requests (openshift#1505) f6c891d Allow updates of instances that failed a previous update. (openshift#1502) 5107086 Use Plan ID from ExternalProperties when deprovisioning instance (openshift#1501) d897c60 Adding message builder for expected event strings (openshift#1465) 9f6152e update osb client and freeze gorilla context (openshift#1496) c63277e Add unit tests verifying deleting a resource with an on-going operation or in orphan mitigation. (openshift#1490) 4ecca16 Pretty logging for controller_instance.go (openshift#1472) c232db4 Register qemu statics when building non-amd64 images (openshift#1494) 0e54c57 fix 'Spring Cloud Services -> Configuring with Vault' link in docs (openshift#1495) REVERT: 892b0368f0 origin build: add origin tooling git-subtree-dir: cmd/service-catalog/go/src/github.com/kubernetes-incubator/service-catalog git-subtree-split: 3064247d0544aa43f976d93caea0a11771434ef7
…on or in orphan mitigation. (openshift#1490)
Running Vagrant with libvirt driver causes OpenShift to produce a lot of these messages:
(there is much more)....
Also I can see that pods gets stuck in Pending state and then keep restarting (docker-registry for example).
The text was updated successfully, but these errors were encountered: