juju-quickstart: bad API server response: 'NoneType' object is not iterable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Francesco Banconi | ||
1.21 |
Fix Released
|
Critical
|
Francesco Banconi | ||
1.22 |
Fix Released
|
Critical
|
Francesco Banconi | ||
juju-quickstart |
Invalid
|
Critical
|
Francesco Banconi |
Bug Description
The following error is seen on multiple substrates (AWS, Joyent, HP, MaaS).
First seen with gitbranch:
juju --show-log quickstart -e test-release-joyent --constraints mem=2G --no-browser /var/lib/
2015-02-10 13:38:09 INFO juju.cmd supercommand.go:37 running juju [1.22-beta3-
13:38:10 WARNING platform_
juju quickstart v1.6.0
contents loaded for bundle landscape-scalable (services: 6)
ssh-agent has been started.
To interact with Juju or quickstart again after quickstart
finishes, please run the following in a terminal to start ssh-agent:
eval `ssh-agent`
bootstrapping the test-release-joyent environment
retrieving the environment status
retrieving the Juju API address
retrieving the Juju environment credentials
connecting to wss://72.
environment type: joyent
bootstrap node series: trusty
charm URL: cs:trusty/
requesting juju-gui deployment
juju-gui deployment request accepted
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
unit placed on 72.2.113.157
machine 0 is started
juju-gui/0 is ready on machine 0
Juju GUI URL: https:/
username: admin
password: 3df26d0e2ad0964
connecting to the Juju GUI server
requesting a deployment of the landscape-scalable bundle with the following services:
haproxy, rabbitmq-server, postgresql, landscape, landscape-msg, apache2
juju-quickstart: error: bad API server response: invalid request: 'NoneType' object is not iterable
2015-02-10 13:41:37 ERROR juju.cmd supercommand.go:411 subprocess encountered error code 1
<class 'subprocess.
Changed in juju-core: | |
status: | New → Invalid |
Changed in juju-quickstart: | |
status: | New → Invalid |
Changed in juju-core: | |
status: | Invalid → New |
Changed in juju-quickstart: | |
status: | Invalid → New |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.23 |
tags: | added: api network regression |
Changed in juju-core: | |
assignee: | nobody → Francesco Banconi (frankban) |
status: | Triaged → In Progress |
tags: | added: ci |
Changed in juju-core: | |
importance: | High → Critical |
Changed in juju-core: | |
importance: | Critical → High |
Changed in juju-core: | |
importance: | High → Critical |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-quickstart: | |
status: | Triaged → Invalid |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
Changed in juju-core: | |
milestone: | 1.23 → 1.23-beta1 |
John, can you confirm that this is against the 1.22 branch. Did this test pass in 1.21? Is there a way to see the results and determine if this is due to a quickstart update or a juju update or is this a new test?
We'll chase down and attempt to duplicate, but having more info can save us some time chasing our tails if you know more details.
Thanks