Ubuntu
magnum package

Kubernetes cluster created with "UNHEALTHY" health status

Bug #1825315 reported by Rajat Sharma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
magnum (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have followed (https://docs.openstack.org/magnum/latest/install/launch-instance.html) to create a Kuberetes cluster with "Fedora" OS-Distro but the cluster is created with "UNHEALTHY" health status.

Kubelet logs:
go:75] Connecting to docker on unix:///var/run/docker.sock
go:104] Start docker client with request timeout=2m0s
service.go:545] Hairpin mode set to "promiscuous-bridge" but kubenet is not enabled, falling back to "hairpin-veth"
service.go:238] Hairpin mode set to "hairpin-veth"
172] Unable to update cni config: No networks found in /etc/cni/net.d
172] Unable to update cni config: No networks found in /etc/cni/net.d
service.go:253] Docker cri networking managed by cni

I have tried using both driver(Flannel and Calico), and tried to manually setup CNI but its still not working.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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