[Bug 1393444] [NEW] machine unit connects to apiserver but stays in agent-state: pending

[JuanJo Ciarlante]

Public bug reported:

FYI this is the same environment from lp#1392810 (1.18->1.19->1.20),
juju version: 1.20.11-trusty-amd64

New units deployed (to LXC over maas) stay at "agent-state: pending":
http://paste.ubuntu.com/9057045/

#1 TCP connects ok to node0:17070
- at the unit:
ubuntu at juju-machine-18-lxc-5:~$ netstat -tn
tcp   0      0 x.x.x.167:57937 x.x.x.8:17070   ESTABLISHED

- at node0:
ubunte at node0:~$ sudo netstat -tnp|grep 167
tcp6  0   3807 x.x.x.8:17070   x.x.x.167:57937 ESTABLISHED 1993/jujud

Interesting there is that node0's socket tcp receive queue (3807 bytes)
is not being read by jujud.

#2 machine-0.log:
- nothing shows at unit's connection time
(ie restart  jujud-machine-18-lxc-5)

- after 4~5minutes, connection drops, and this is logged:
2014-11-17 14:28:56 ERROR juju.state.apiserver.common resource.go:102 error stopping *apiserver.pingTimeout resource: ping timeout

** Affects: juju-core
     Importance: High
         Status: Triaged

** Affects: juju-core (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: canonical-bootstack canonical-is lxc upgrade-juju

** Tags added: canonical-bootstack

** Tags added: canonical-is

** Summary changed:

- machine unit connects to apiserver but doesn't deploy service
+ machine unit connects to apiserver but stays in agent-state: pending

-- 
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