@sinzui: closing this as invalid, as I later confirmed this to be a MTU
issue.
** Changed in: juju-core
Status: Triaged => Invalid
** Changed in: juju-core (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
** Changed in: juju-core
Milestone: 1.23 => None
** Changed in: juju-core
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1393444
Title:
machine
** Changed in: juju-core
Milestone: 1.22-alpha1 => 1.23
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1393444
Title:
machine unit connects to apiserver but stays in agent-sta
This deployment has 2 metal nodes hosting LXC units (machine:
0, 18), then 'juju deploy cs:ubuntu --to lxc:0' does ok, while
'--to lxc:18' was consistently failing as described above.
FYI I've worked around this by removing machine 18 down to
'maas ready' and reacquiring it from juju, now all new
strace at both sides (grepped for specific sockets):
http://paste.ubuntu.com/9057691/,
mind the subsecond date diff.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1393444
Title:
/var/log/juju/machine-18-lxc-5.log: http://paste.ubuntu.com/9057287/
NOTE there the repeated log stanzas are because of my manual restarts.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/
** Also affects: juju-core
Importance: Undecided
Status: New
** Changed in: juju-core
Status: New => Triaged
** Changed in: juju-core
Importance: Undecided => High
** Tags added: upgrade-juju
** Tags added: lxc
** Changed in: juju-core
Milestone: None => 1.22
--
You r
