Public bug reported:
juju-quickstart appears to be broken on Trusty when on defaults. This is
a regression from Trusty development, since I tested this before upload
and know that it used to work.
The last message I see is: machine 1 provisioning is pending
juju status says:
environment: local
machines:
"0":
agent-state: started
agent-version: 1.18.1.1
dns-name: localhost
instance-id: localhost
series: trusty
"1":
instance-id: pending
series: precise
services:
juju-gui:
charm: cs:precise/juju-gui-90
exposed: true
units:
juju-gui/0:
agent-state: pending
machine: "1"
/var/log/juju-ubuntu-local/all-machines.log is full of:
machine-0: 2014-05-05 19:47:37 ERROR juju runner.go:220 worker: exited
"environ-provisioner": failed to process updated machines: cannot start
machine 1: no matching tools available
If I destroy the environment and try creating things by hand, "juju add-
machine" works, but deploys a trusty node by default. I guess the
precise tools aren't being uploaded and aren't available to the
bootstrap node?
** Affects: juju-quickstart
Importance: Undecided
Status: New
** Affects: juju-quickstart (Ubuntu)
Importance: Undecided
Status: New
** Also affects: juju-quickstart
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316291
Title:
juju-quickstart hangs on "machine 1 provisioning is pending"
To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-quickstart/+bug/1316291/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
