juju proxy fails silently when socat not installed

Bug #1912348 reported by Luke Marsden
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Thomas Miller

Bug Description

https://github.com/juju/juju/pull/12512 silently introduced a dependency on socat

13:35:39 DEBUG juju.kubernetes.klog klog.go:34 an error occurred forwarding 35317 -> 17070: error forwarding port 17070 to pod 9044cea485b2ee040caf51ffb1c648bc78e52e64a04e76d36681932634fbe96e, uid : unable to do port forwarding: socat not found

eventually:

ERROR unable to contact api server after 61 attempts: unable to connect to API: EOF

Had to run `juju bootstrap --debug` to see this, it should have been shown as an error, then I'd have known what to do (install socat)!

Tags: k8s
Ian Booth (wallyworld)
Changed in juju:
milestone: none → 2.9-rc4
status: New → Triaged
importance: Undecided → High
assignee: nobody → Thomas Miller (tlmiller)
tags: added: k8s
Revision history for this message
Thomas Miller (tlmiller) wrote :
Changed in juju:
status: Triaged → In Progress
status: In Progress → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
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.