juju 1.18.0 environment unusable after bootstrap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Invalid
|
Critical
|
Unassigned |
Bug Description
Fresh trusty beta 2 machine, juju 1.18.0, bootstraping a local environment fails
ubuntu@
A boilerplate environment configuration file has been written to /home/ubuntu/
Edit the file to configure your juju environment and run bootstrap.
iubuntu@
+ /usr/bin/juju destroy-environment -y local
ERROR failed to destroy environment "local"
If the environment is unusable, then you may run
juju destroy-environment --force
to forcefully destroy the environment. Upon doing so, review
your environment provider console for any resources that need
to be cleaned up.
ERROR environment is not bootstrapped
+ true
+ /usr/bin/juju bootstrap
uploading tools for series [trusty precise]
Logging to /home/ubuntu/
Starting MongoDB server (juju-db-
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-
+ /usr/bin/juju deploy --repository=
Added charm "local:
+ /usr/bin/juju deploy --repository=
Added charm "local:
+ /usr/bin/juju deploy --repository=
Added charm "local:
+ /usr/bin/juju deploy --repository=
Added charm "local:
+ /usr/bin/juju set mysql dataset-size=1G
+ /usr/bin/juju add-relation sugarcrm:database mysql:db
+ /usr/bin/juju add-relation sugarcrm memcached
+ /usr/bin/juju add-relation sugarcrm haproxy
+ /usr/bin/juju expose haproxy
ubuntu@
ERROR Unable to connect to environment "".
Please check your credentials or use 'juju bootstrap' to create a new environment.
Error details:
control-bucket: expected string, got nothing
This was PEBCAK, the demo script uses a JUJU_ENV which is not exported outside the script