Description of problem: After installing OSE3 on atomic host using BYO playbook, this is what I see in service log: > # systemctl status atomic-openshift-node.service -l > ● atomic-openshift-node.service > Loaded: loaded (/etc/systemd/system/atomic-openshift-node.service; enabled; vendor preset: disabled) > Active: active (running) since Mon 2016-04-18 03:42:04 UTC; 1 day 8h ago > Process: 9256 ExecStop=/usr/bin/docker stop atomic-openshift-node (code=exited, status=1/FAILURE) > Process: 9552 ExecStartPost=/usr/bin/sleep 10 (code=exited, status=0/SUCCESS) > Process: 9542 ExecStartPre=/usr/bin/docker rm -f atomic-openshift-node (code=exited, status=0/SUCCESS) > Main PID: 9551 (docker) > Memory: 6.4M > CGroup: /system.slice/atomic-openshift-node.service > └─9551 /usr/bin/docker run --name atomic-openshift-node --rm --privileged --net=host --pid=host --env-file=/etc/sysconfig/atomic-openshift-node -v /:/rootfs:ro -e CONFIG_FILE=/etc/origin/node/node-config.yaml -e OPTIONS=--loglevel=5 -e HOST=/rootfs -e HOST_ETC=/host-etc -v /var/lib/origin:/var/lib/origin -v /etc/origin/node:/etc/origin/node -v /etc/localtime:/etc/localtime:ro -v /etc/machine-id:/etc/machine-id:ro -v /run:/run -v /sys:/sys:ro -v /usr/bin/docker:/usr/bin/docker:ro -v /var/lib/docker:/var/lib/docker -v /lib/modules:/lib/modules -v /etc/origin/openvswitch:/etc/openvswitch -v /etc/origin/sdn:/etc/openshift-sdn -v /etc/systemd/system:/host-etc/systemd/system -v /var/log:/var/log -v /dev:/dev openshift3/node:v3.2.0.16 > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194020 9600 docker.go:363] Docker Container: /tiny_babbage is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194040 9600 docker.go:363] Docker Container: /loving_curie is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194047 9600 docker.go:363] Docker Container: /goofy_yonath is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194053 9600 docker.go:363] Docker Container: /nostalgic_noyce is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194059 9600 docker.go:363] Docker Container: /desperate_bhaskara is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194064 9600 docker.go:363] Docker Container: /atomic-openshift-node is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194073 9600 docker.go:363] Docker Container: /openvswitch is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194082 9600 docker.go:363] Docker Container: /atomic-openshift-master is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194092 9600 docker.go:363] Docker Container: /furious_dijkstra is not managed by kubelet. > Apr 19 11:50:32 openshift-114.lab.sjc.redhat.com atomic-openshift-node[9551]: I0419 11:50:32.194102 9600 docker.go:363] Docker Container: /sleepy_khorana is not managed by kubelet. Version-Release number of selected component (if applicable): 3.2.0.16 How reproducible: always Additional info: Otherwise environment appears to be working properly. But error messages are scary and may indicate a real issue.
This is a harmless message. It's just indicating that there are some Docker containers on the node that were not created by Kubernetes. This message is displayed at loglevel 3. We could consider lowering the level to something like 5 if that would be helpful.
Ok, thank you. I don't have opinion about log level. Might be good to be documented if not done already.
Reading openshift and kubernetes docs for a while. It looks like this behaviour is not documented anywhere or it is hard to find it. Aleksandar, would it be enough to document this behaviour? This is suitable for kubelet and his management of containers. Partially, garbage collector mentiones [1]: "Containers that are not managed by kubelet are not subject to container garbage collection." Nothing else so far. [1] http://kubernetes.io/docs/admin/garbage-collection/
Undirectly, it is state here [1]: "The kubelet takes a set of PodSpecs that are provided through various mechanisms (primarily through the apiserver) and ensures that the containers described in those PodSpecs are running and healthy." Stating "kubelet takes care of containers described in the pod specifications." [1] http://kubernetes.io/docs/admin/kubelet/
Other piece of info [1]: "Many of these containers run under the management of the kubelet binary, which attempts to keep containers running, even if they fail. So, in order to turn down the cluster, you need to first kill the kubelet container, and then any other containers." Stating kubelet runs kubelet containers. [1] http://kubernetes.io/docs/getting-started-guides/docker/ Information you are looking for is in the documentation but broken apart on many places.
Nothing tells users why these messages are printed out and if they need to do anything to correct that. The above quotes do not indicate whether which containers are ok to be listed as such and which not. What are these having to do with OpenShift "goofy_yonath", "loving_curie"? I don't say they don't belong. It's just not clear and I as a user would be wondering what are these and is it normal to see such messages.
I mean that a little more explanation in documentation is what we need in my opinion.
Upstream PR here: https://github.com/kubernetes/kubernetes/pull/30435. Once merged, it can be rebased in Origin.
Merged upstream. Once the openshift gets rebased, this can be closed.