windows tunnel: error adding route: The object exists already. #8507
Comments
|
Yeah, weird. I rebooted after a security install and got this instead: |
tstromberg
changed the title
tstromberg
added
area/tunnel
|
@doublefx - Did the tunnel still work with this error message, or did it fail entirely? |
tstromberg
changed the title
tstromberg
changed the title
tstromberg
added
the
priority/backlog
|
@tstromberg It did fail entirely, no tunnel was opened. |
|
@doublefx do you have this issue with docker driver and laters verison of minikube on windows? and do you have a firewall enabled? |
|
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
k8s-ci-robot
added
lifecycle/rotten
|
Hey @doublefx are you still seeing this issue? If so, could you provide the following info:
Thank you! |
priyawadhwa
added
triage/needs-information
|
Hi @doublefx, we haven't heard back from you, do you still have this issue? I will close this issue for now but feel free to reopen when you feel ready to provide more information. |
Steps to reproduce the issue:
Full output of failed command:
I0617 21:36:02.725276 18768 mustload.go:64] Loading cluster: minikube
I0617 21:36:02.727274 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
I0617 21:36:03.226240 18768 main.go:110] libmachine: [stdout =====>] : Running
I0617 21:36:03.226883 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:03.226883 18768 host.go:65] Checking if "minikube" exists ...
I0617 21:36:03.227884 18768 api_server.go:145] Checking apiserver status ...
I0617 21:36:03.249918 18768 ssh_runner.go:148] Run: sudo pgrep -xnf kube-apiserver.minikube.
I0617 21:36:03.250914 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
I0617 21:36:03.790202 18768 main.go:110] libmachine: [stdout =====>] : Running
I0617 21:36:03.790202 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:03.791169 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[0]
I0617 21:36:04.473864 18768 main.go:110] libmachine: [stdout =====>] : 172.30.159.127
I0617 21:36:04.474869 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:04.475866 18768 sshutil.go:44] new ssh client: &{IP:172.30.159.127 Port:22 SSHKeyPath:C:\Users\doublefx.minikube\machines\minikube\id_rsa Username:docker}
I0617 21:36:04.596486 18768 ssh_runner.go:188] Completed: sudo pgrep -xnf kube-apiserver.minikube.: (1.3455722s)
I0617 21:36:04.621490 18768 ssh_runner.go:148] Run: sudo egrep ^[0-9]+:freezer: /proc/4014/cgroup
I0617 21:36:04.627525 18768 api_server.go:161] apiserver freezer: "9:freezer:/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod8f362b6d7d89dab1420a57093421b29a.slice/docker-ae0c1011cdb729d4cf9446cf65a586fef062b84531dfba37cd33f0fa84e2dd89.scope"
I0617 21:36:04.655503 18768 ssh_runner.go:148] Run: sudo cat /sys/fs/cgroup/freezer/kubepods.slice/kubepods-burstable.slice/kubepods-burstable-pod8f362b6d7d89dab1420a57093421b29a.slice/docker-ae0c1011cdb729d4cf9446cf65a586fef062b84531dfba37cd33f0fa84e2dd89.scope/freezer.state
I0617 21:36:04.664490 18768 api_server.go:183] freezer state: "THAWED"
I0617 21:36:04.664490 18768 api_server.go:193] Checking apiserver healthz at https://172.30.159.127:8443/healthz ...
I0617 21:36:04.675498 18768 api_server.go:213] https://172.30.159.127:8443/healthz returned 200:
ok
I0617 21:36:04.677492 18768 tunnel.go:56] Checking for tunnels to cleanup...
I0617 21:36:04.690525 18768 host.go:65] Checking if "minikube" exists ...
I0617 21:36:04.691489 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
I0617 21:36:05.189036 18768 main.go:110] libmachine: [stdout =====>] : Running
I0617 21:36:05.189668 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:05.190670 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
I0617 21:36:05.708256 18768 main.go:110] libmachine: [stdout =====>] : Running
I0617 21:36:05.708256 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:05.709256 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[0]
I0617 21:36:06.369761 18768 main.go:110] libmachine: [stdout =====>] : 172.30.159.127
I0617 21:36:06.369761 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:06.370752 18768 tunnel_manager.go:71] Setting up tunnel...
I0617 21:36:06.370752 18768 tunnel_manager.go:81] Started minikube tunnel.
I0617 21:36:11.376932 18768 host.go:65] Checking if "minikube" exists ...
I0617 21:36:11.377880 18768 main.go:110] libmachine: [executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
I0617 21:36:11.896197 18768 main.go:110] libmachine: [stdout =====>] : Running
I0617 21:36:11.896197 18768 main.go:110] libmachine: [stderr =====>] :
I0617 21:36:12.435075 18768 route_windows.go:47] Adding route for CIDR 10.96.0.0/12 to gateway 172.30.159.127
I0617 21:36:12.448977 18768 route_windows.go:49] About to run command: [route ADD 10.96.0.0 MASK 255.240.0.0 172.30.159.127]
Status:
machine: minikube
pid: 18768
route: 10.96.0.0/12 -> 172.30.159.127
minikube: Running
services: []
errors:
minikube: no errors
router: error adding route: L'ajout de l'itin�raire a �chou��: L'objet existe d�j�.
, 3
loadbalancer emulator: no errors
I0617 21:36:17.406065 18768 loadbalancer_patcher.go:79] ambassador is type LoadBalancer.
Note: "L'ajout de l'itin�raire a �chou��: L'objet existe d�j�" means: Adding the route has failed: The oject exists already.
Optional: Full output of
minikube logscommand:The text was updated successfully, but these errors were encountered: