Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tunnel: needs clean after delete router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 #7900

Closed
medyagh opened this issue Apr 25, 2020 · 2 comments · Fixed by #7946
Closed

Tunnel: needs clean after delete router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 #7900

medyagh opened this issue Apr 25, 2020 · 2 comments · Fixed by #7946
Assignees
@govargo
Labels
area/tunnel Support for the tunnel command co/service issues related to the service feature kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
v1.10.0

Comments

@medyagh
Copy link
Member

medyagh commented Apr 25, 2020

after deleting minikube, and starting it again and deploying my service
I saw :

~$ minikube tunnel
Status:	
	machine: minikube
	pid: 764782
	route: 10.96.0.0/12 -> 172.17.0.2
	minikube: Running
	services: []
    errors: 
		minikube: no errors
		router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 
		loadbalancer emulator: no errors
Status:	
	machine: minikube
	pid: 764782
	route: 10.96.0.0/12 -> 172.17.0.2
	minikube: Running
	services: []
    errors: 
		minikube: no errors
		router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 
		loadbalancer emulator: no errors

I was able to fix it by running

minikube tunnel -c

minikube should do an auto-clean up, so the user doesnt have to do a clean up after each minikube run or delete.
@medyagh medyagh added kind/bug Categorizes issue or PR as related to a bug. co/service issues related to the service feature labels Apr 25, 2020
@medyagh medyagh added this to the v1.10.0 milestone Apr 25, 2020
@medyagh medyagh changed the title Tunnel: router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 Tunnel after delete needs clean: router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 Apr 25, 2020
@medyagh medyagh changed the title Tunnel after delete needs clean: router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 Tunnel: needs clean after delete router: conflicting route: 10.96.0.0/12 via 172.17.0.3 dev docker0 Apr 25, 2020
@tstromberg
Copy link
Contributor

I've seen some similar issues as well. tunnel should just clear conflicting routes by default, IMHO. If it breaks someone, we can always add a flag to disable it.

@tstromberg tstromberg added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 26, 2020
@tstromberg
Copy link
Contributor

Should this be bumped to v1.11?

@govargo govargo self-assigned this Apr 30, 2020
@govargo govargo mentioned this issue Apr 30, 2020
Merged
@govargo govargo added the area/tunnel Support for the tunnel command label Apr 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@govargo govargo

Labels
area/tunnel Support for the tunnel command co/service issues related to the service feature kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
v1.10.0
Development

Successfully merging a pull request may close this issue.

Change tunnel cleanup flag default to true for auto tunnel cleanup
3 participants
@tstromberg @medyagh @govargo