juju.-gui fails with a config-changed error when used under juju 1.21alpha
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Critical
|
Unassigned | ||
juju-gui |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
http://
Attempts to deploy the GUI with juju-core debian packages for juju-core 1.21alpha built by CI from gitbranch:
2014-09-08 12:43:19 INFO unit.juju-
2014-09-08 12:43:19 INFO unit.juju-
2014-09-08 12:43:19 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 INFO unit.juju-
2014-09-08 12:43:20 ERROR juju.worker.uniter uniter.go:566 hook failed: exit status 1
2014-09-08 12:49:48 ERROR juju.api.watcher watcher.go:83 error trying to stop watcher: connection is shut down
More log files are attaeched, as well as the debian packages
Changed in juju-core: | |
importance: | Undecided → Critical |
status: | New → Triaged |
milestone: | none → 1.21-alpha2 |
milestone: | 1.21-alpha2 → next-stable |
Changed in juju-core: | |
milestone: | 1.21-alpha2 → 1.21-alpha1 |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
This looks like either there's a bug in juju around port opening or there was something else on that vagrant box using the port before the GUI could gain access to it. I'm not as familiar with the vagrant setup. I thought at one point the GUI was auto setup when you did a vagrant install. If this is true is it possible you were actually deploying a second GUI?
I'd like to know more about the Vagrant setup and exact steps to reproduce from the start to debug farther. I'm going to make as incomplete at the moment. Thanks for the bug report and I look forward to the updated information on the environment/vagrant setup so we can attempt to duplicate easier.