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 LXC units there behave normally. IMO still worth digging what state bits left there for that machine were triggering this issue, copied a juju backup tarball to ~natefinch in case this is feasible. -- 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-state: pending To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1393444/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
