container addressability Can't juju ssh to lxd-placed container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned |
Bug Description
If I deploy into a container of a machine, I can't `juju ssh` into it.
Steps to reproduce:
1. Deploy some stuff. In my case, I deployed ceph on openstack.
2. juju deploy ubuntu --series trusty --to lxc:3
Then I get:
[Units]
ID WORKLOAD-STATUS JUJU-STATUS VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
ceph/1 unknown idle 2.0-beta7.1 1 10.55.32.62
ceph/2 unknown idle 2.0-beta7.1 2 10.55.32.72
ceph/3 unknown idle 2.0-beta7.1 3 10.55.32.85
demo-client/2 unknown idle 2.0-beta7.1 3/lxd/0 10.0.4.147
3. Can't ssh in to the container
$ juju ssh demo-client/2
ssh: connect to host 10.0.4.147 port 22: Connection timed out
I *think* I remember being able to do this with lxc: placed units in juju 1.x.
See this to track the recent form of the regression
http://
tags: | added: rc1 |
tags: | added: ci regression |
tags: | added: ssh |
Changed in juju-core: | |
importance: | High → Critical |
description: | updated |
Changed in juju-core: | |
milestone: | none → 2.0-beta8 |
Changed in juju-core: | |
milestone: | 2.0-beta8 → 2.0.0 |
importance: | Critical → High |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
tags: | added: canonical-is |
Changed in juju: | |
status: | New → Triaged |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | New → Triaged |
milestone: | 2.1.0 → 2.2.0 |
summary: |
- Can't juju ssh to lxd-placed container + container addressability Can't juju ssh to lxd-placed container |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
tags: | added: container-addressability |
Changed in juju: | |
milestone: | 2.2-rc1 → none |
Just deployed OpenStack and "juju ssh ceph-mon/0" worked fine. It was created on 1/lxc/0 (this is a xenial machine, so it is a lxd managed lxc).
Tested with master + some routing fixes. I don't think the routing fixes will have had any impact though because they only fixed bonded interfaces.