incompatible with kube. crap like this:
Apr 16 09:08:02 localhost.localdomain systemd[1]: libcontainer-7691-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
I backported https://github.com/kubernetes/kubernetes/pull/61926 on top of 1.9.6 and even with the latest docker installed the kubelet still complains. Not sure if it the issue is still in docker or something is missing in Kubernetes.
Even just with the docker-1.13.1-52.git89b0e65.fc29.x86_64 there are errors:
Apr 17 12:33:39 f28-k8s-test.localdomain dockerd-current[768]: container_linux.go:247: starting container process caused "process_linux.go:258: applying cgroup configuration for process caused \"No such device or address\""
Given the above feedback, I'm giving a -1 so this gets unpushed; we clearly need more work to fix everything for the systemd change. It'd be good if folks could work together to produce one complete update with all the necessary changes in it at once. In the meantime, it looks like the systemd change will be reverted until this can be fixed properly.
This update has been submitted for testing by lsm5.
I used
rpm-ostree override replace
on F28 Atomic Host Beta to install this update.docker run -it docker.io/busybox echo "PASS"
worked for meBut I still can't do
oc cluster up
usingorigin-clients-3.6.0-1
. Fails with the same error in BZ 1558425I don't know why bodhi won't take my mixed karma...
Anyways, the BZ is not fixed, but as I said earlier, simple 'docker run' seems to work ok.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
incompatible with kube. crap like this: Apr 16 09:08:02 localhost.localdomain systemd[1]: libcontainer-7691-systemd-test-default-dependencies.scope: Scope has no PIDs. Refusing.
I backported https://github.com/kubernetes/kubernetes/pull/61926 on top of 1.9.6 and even with the latest docker installed the kubelet still complains. Not sure if it the issue is still in docker or something is missing in Kubernetes.
docker-1.13.1-51.git4032bd5.fc28.x86_64 works. -52 does not. Maybe kube can be changed, but right now, if this is released kube will not work.
admittedly, kube is already broken in f28 because of systemd regression....
Even just with the docker-1.13.1-52.git89b0e65.fc29.x86_64 there are errors:
Given the above feedback, I'm giving a -1 so this gets unpushed; we clearly need more work to fix everything for the systemd change. It'd be good if folks could work together to produce one complete update with all the necessary changes in it at once. In the meantime, it looks like the systemd change will be reverted until this can be fixed properly.
This update has been obsoleted.
see https://bugzilla.redhat.com/show_bug.cgi?id=1568594