New subject: [Bug 1200919] kube-proxy should start when network is ready

11 Mar 2015

https://bugzilla.redhat.com/show_bug.cgi?id=1200919
Bug ID: 1200919
           Summary: kube-proxy should start when network is ready
           Product: Fedora
           Version: rawhide
         Component: kubernetes
          Assignee: jchaloup@redhat.com
          Reporter: leon@bcl.bz
        QA Contact: extras-qa@fedoraproject.org
                CC: eparis@redhat.com, golang@lists.fedoraproject.org,
                    jchaloup@redhat.com, lsm5@redhat.com,
                    nhorman@redhat.com, vbatts@redhat.com
Description of problem:
kube-proxy is unable to start if network interface is not initialised yet
Version-Release number of selected component (if applicable):
kubernetes-0.12.0-0.4.gita4d871a.fc23
How reproducible:
Steps to Reproduce:
1. yum install kubernet
2. configure kube-proxy (etcd url, etc), run systemctl start kube-proxy and
make sure it's running properly
3. systemctl enable kube-proxy
4. reboot
Actual results:
traceback in log, systemctl status kube-proxy say it's not running
Expected results:
no traceback in logs, systemctl status kube-proxy should say it's running
properly
Additional info:
This patch helps:

--- contrib/init/systemd/kube-proxy.service.orig        2015-03-07
20:33:29.765178753 +0300
+++ contrib/init/systemd/kube-proxy.service     2015-03-07 20:34:19.008530113
+0300
@@ -1,6 +1,7 @@
 [Unit]
 Description=Kubernetes Kube-Proxy Server
 Documentation=https://github.com/GoogleCloudPlatform/kubernetes
+After=network.target
[Service]
 EnvironmentFile=-/etc/kubernetes/config
-- 
You are receiving this mail because:
You are on the CC list for the bug.

    

[Bug 1200919] New: kube-proxy should start when network is ready