juju scp broken in 2.9.24 release testing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
High
|
Yang Kelvin Liu |
Bug Description
As seen in testrun:
https:/
Juju fails to scp files from the kubernetes-master unit.
-------
2022-02-12-01:05:50 root ERROR [localhost] Command failed: juju scp -m foundation-
2022-02-12-01:05:50 root ERROR [localhost] STDOUT follows:
b''
2022-02-12-01:05:50 root ERROR [localhost] STDERR follows:
ERROR cannot connect to any address: [172.16.0.110:22]
-------
Crashdumps:
https:/
The crashdumps are empty, even though `juju crashdump` uses scp instead of juju scp.
All occurrences of this bug:
https:/
description: | updated |
Changed in juju: | |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
Kubernetes containers don't run ssh for you to SCP the content from a container.
Juju fakes ssh support and scp support by mapping it to other kubernetes primitives (exec, IIRC)
So crashdump won't work for those cotnainers. I don't know why it is actually trying to connect to :22, since there isn't anything there.