** Description changed:

+ [Impact]
+ 
+ If the control-bucket field is not present in the environments.yaml file
+ juju will generate one.  This patch makes control-bucket an optional
+ field for juju-quickstart.
+ 
+ [Test Case]
+  * Create an ec2 environment in $JUJU_HOME/environments.yaml that does not 
have a control-bucket.
+  * Bootstrap that environment using juju, not juju-quickstart.
+  * Ensure a control-bucket is in the generated environments/<envname>.jenv 
file.
+  * Run juju-quickstart using the existing environment and see that no error 
is raised.
+ 
+ [Regression Potential]
+ 
+ The overly strict error checking has been relaxed to stay in sync with
+ juju-core. Potential for regression is minimal.
+ 
+ [Original Bug Report]
+ 
  Having bootstraped an amazon environment with juju, I run juju-
  quickstart and get the following error
  
  $ juju-quickstart
  usage: juju-quickstart [-h] [-e ENV_NAME] [-n BUNDLE_NAME] [-i]
-                        [--environments-file ENV_FILE]
-                        [--gui-charm-url CHARM_URL] [--no-browser]
-                        [--distro-only] [--ppa] [--version] [--debug]
-                        [--description]
-                        [bundle]
+                        [--environments-file ENV_FILE]
+                        [--gui-charm-url CHARM_URL] [--no-browser]
+                        [--distro-only] [--ppa] [--version] [--debug]
+                        [--description]
+                        [bundle]
  juju-quickstart: error: cannot use the amazon environment:
  a value is required for the control bucket field
  
  I checked that I did have a value for `control-bucket` in
  ~/.juju/environments/amazon.jenv and ran
  
  $ juju-quickstart -i
  
  There I saw that some properties were copied from environments.yaml (it
  apparently did not use the .jenv file) and some not and that it needed
  the `control-bucket` value (which is not defined in environments.yaml).
  
  So, properties like `access-key`, `secret-key`, `type` were extracted 
successfully from environments.yam but not the `region`.
  And it ignored the bucket field in environments/amazon.jenv (which was 
defined by me).
  
- 
  ENV info:
  
  $ juju version
  1.19.0-trusty-amd64
  
  $ juju-quickstart --version
  juju-quickstart 1.3.1

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-quickstart in Ubuntu.
https://bugs.launchpad.net/bugs/1309678

Title:
  a value is required for the control bucket field

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-quickstart/+bug/1309678/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to