juju 1.18.0 environment unusable after bootstrap

Bug #1305365 reported by Dave Cheney
6
This bug affects 1 person
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@ip-10-249-72-34:~$ juju init
A boilerplate environment configuration file has been written to /home/ubuntu/.juju/environments.yaml.
Edit the file to configure your juju environment and run bootstrap.
iubuntu@ip-10-249-72-34:~$ bash demo.bash
+ /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/.juju/local/cloud-init-output.log on remote host
Starting MongoDB server (juju-db-ubuntu-local)
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-ubuntu-local)
+ /usr/bin/juju deploy --repository=/home/ubuntu/demo local:trusty/sugarcrm
Added charm "local:trusty/sugarcrm-0" to the environment.
+ /usr/bin/juju deploy --repository=/home/ubuntu/demo local:trusty/mysql
Added charm "local:trusty/mysql-311" to the environment.
+ /usr/bin/juju deploy --repository=/home/ubuntu/demo local:trusty/memcached
Added charm "local:trusty/memcached-28" to the environment.
+ /usr/bin/juju deploy --repository=/home/ubuntu/demo local:trusty/haproxy
Added charm "local:trusty/haproxy-28" to the environment.
+ /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@ip-10-249-72-34:~$ juju status
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

Revision history for this message
Dave Cheney (dave-cheney) wrote :

This was PEBCAK, the demo script uses a JUJU_ENV which is not exported outside the script

Changed in juju-core:
status: Triaged → Invalid
Revision history for this message
Dave Cheney (dave-cheney) wrote :

Hmm, this is actually a bug. By default the juju init sets the environment to "amazon", the demo script is setting JUJU_ENV to local, but the fact that juju status reports the environment as "" is the bug.

Changed in juju-core:
status: Invalid → Incomplete
Revision history for this message
Ian Booth (wallyworld) wrote :

File new bug 1305385 for the status output issue.
Closing this one as Invalid.

Changed in juju-core:
status: Incomplete → Invalid
milestone: 1.18.1 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.