kube-proxy won't start with lxd-profile

Bug #1919091 reported by Jorge Niedbalski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubernetes Control Plane Charm
Incomplete
Undecided
Unassigned

Bug Description

[Description]

Latest master
Latest charmed-kubernetes

kube-proxy won't start on kubernetes-worker units when using this
LXD profile https://github.com/charmed-kubernetes/charm-kubernetes-master/blob/master/lxd-profile.yaml

units will fail with the following message:

I0314 19:16:08.784246 64633 conntrack.go:100] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400
F0314 19:16:08.784459 64633 server.go:495] open /proc/sys/net/netfilter/nf_conntrack_tcp_timeout_established: no such file or directory

Revision history for this message
George Kraft (cynerva) wrote :

I'm unable to reproduce this. I can deploy kubernetes-master on LXD (letting Juju apply the LXD profile automatically) and I do not encounter the fatal error:

I0323 19:02:21.097949 55356 conntrack.go:100] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_established' to 86400
I0323 19:02:21.098058 55356 conntrack.go:100] Set sysctl 'net/netfilter/nf_conntrack_tcp_timeout_close_wait' to 3600
I0323 19:02:21.174632 55356 config.go:315] Starting service config controller
...

Please provide reproduction steps.

Changed in charm-kubernetes-master:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.