juju 2 unavailable after bootstrap - possible infinite recursion loop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Critical
|
Dimiter Naydenov |
Bug Description
Today I hit a bit of an odd bug with juju 2 and maas 2 on Xenial - after bootstrapping, juju status seems fine, but I'm unable to deploy anything to it. The error messages are a little strange, it seems to mostly throw:
ERROR upgrade in progress (upgrade in progress)
Looking on the machine-0 logs, I see the following:
2016/10/21 01:08:23 http: TLS handshake error from x.y.z.42:52912: remote error: bad certificate
runtime: goroutine stack exceeds 1000000000-byte limit
fatal error: stack overflow
and then a 1000s of line stack trace (which I'll attach). I've had a quick discussion with wallyworld about it, and it appears there's an infinite recursion issue somewhere here.
The possible only interesting bit about the deployment is that the bootstrap nodes have multiple NICs, one theory discussed was that multiple nics and spaces might be missing test coverage for this.
$ dpkg-query -W juju
juju 1:2.0.0-
$ dpkg-query -W maas
maas 2.0.0+bzr5189-
$ lsb_release -d
Description: Ubuntu 16.04.1 LTS
Please let us know if you need any further information.
Changed in juju: | |
milestone: | none → 2.0.1 |
importance: | Undecided → High |
status: | New → Triaged |
assignee: | nobody → Richard Harding (rharding) |
Changed in juju: | |
importance: | High → Critical |
tags: | added: eda |
tags: | added: gap |
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | Richard Harding (rharding) → Dimiter Naydenov (dimitern) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Stack trace from machine-0