Bug 1200919

Summary:	kube-proxy should start when network is ready
Product:	[Fedora] Fedora	Reporter:	Leonid Kanter <leon>
Component:	kubernetes	Assignee:	Jan Chaloupka <jchaloup>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	eparis, golang-updates, jchaloup, lsm5, nhorman, vbatts
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	kubernetes-0.12.0-0.9.git53b25a7.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-26 21:50:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Leonid Kanter 2015-03-11 16:04:49 UTC

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

Comment 1 Eric Paris 2015-03-11 17:11:26 UTC

https://github.com/GoogleCloudPlatform/kubernetes/pull/5293

Comment 2 Jan Chaloupka 2015-03-13 16:04:45 UTC

https://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20150309/1537300.html

Comment 3 Fedora Update System 2015-03-13 16:40:55 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/kubernetes-0.12.0-0.9.git53b25a7.fc22

Comment 4 Fedora Update System 2015-03-13 16:42:12 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/kubernetes-0.12.0-0.9.git53b25a7.fc21

Comment 5 Fedora Update System 2015-03-13 16:43:06 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kubernetes-0.12.0-0.9.git53b25a7.fc20

Comment 6 Fedora Update System 2015-03-14 09:17:05 UTC

Package kubernetes-0.12.0-0.9.git53b25a7.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kubernetes-0.12.0-0.9.git53b25a7.fc20'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3858/kubernetes-0.12.0-0.9.git53b25a7.fc20
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2015-03-26 21:50:35 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2015-03-26 21:53:14 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-03-26 22:02:53 UTC

kubernetes-0.12.0-0.9.git53b25a7.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.