ssh connection is broken when creating kubernates cluster on environment which has vlan using 172.17.0.1 /16 cidr.

Bug #1735096 reported by Gökhan on 2017-11-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Undecided
Gökhan

Bug Description

Sometimes we can use 172.17.0.1/16 cidr on a vlan in our envrionment. When try to create kubernates cluster on this environment, ssh connection to kubemaster is broken because when boot images it creates docker automaticaly with docker0 bridge with 172.17.0.1/16 cidr. Docker is using flannel network so in fact it shouldn't lost ssh connection. then I see that it is order bug. services are started before network config in https://github.com/openstack/magnum/blob/master/magnum/drivers/k8s_fedora_atomic_v1/templates/kubemaster.yaml#L490
so my solution is to write - config: {get_resource: enable_services} line after the https://github.com/openstack/magnum/blob/master/magnum/drivers/k8s_fedora_atomic_v1/templates/kubemaster.yaml#L496 this line.

Gökhan (skylightcoder) on 2017-11-29
Changed in magnum:
assignee: nobody → Gökhan (skylightcoder)
Spyros Trigazis (strigazi) wrote :

When you boot a fedora atomic image without magnum. Do you see the same problem?

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

Other bug subscribers