juju-quickstart

a value is required for the control bucket field

Bug #1309678 reported by Tugdual de Kerviler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-quickstart
Fix Released
High
Brad Crittenden
juju-quickstart (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

[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]
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

See original description

Related branches

lp:~bac/juju-quickstart/1309678
Juju GUI Hackers: Pending requested
Diff: 197 lines (+33/-30)
6 files modified
quickstart/app.py (+10/-8)
quickstart/manage.py (+2/-2)
quickstart/models/envs.py (+2/-2)
quickstart/tests/models/test_envs.py (+2/-3)
quickstart/tests/test_app.py (+8/-6)
quickstart/tests/test_manage.py (+9/-9)
lp:ubuntu/trusty-proposed/juju-quickstart
Richard Harding (rharding)
Changed in juju-quickstart:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Tugdual de Kerviler (dekervit) wrote :

Concerning the `region` attribute not being retrieved, it is probably due to the fact that I entered an invalid value:
`eu-west-1a` instead of `eu-west-1`

Brad Crittenden (bac)
Changed in juju-quickstart:
assignee: nobody → Brad Crittenden (bac)
status: Triaged → In Progress
Revision history for this message
Tugdual de Kerviler (dekervit) wrote :

Sorry, in the last sentence I meant "which was NOT defined by me"

The issue here is just that juju bootstrap generated a property (control-bucket) which juju-quickstart was not able to access or regenerate. Not sure this needs a fix though.

Francesco Banconi (frankban)
Changed in juju-quickstart:
status: In Progress → Fix Released
Brad Crittenden (bac)
description: updated
Revision history for this message
Robie Basak (racb) wrote :

Fixed in juju-quickstart 1.4.0-0ubuntu1 in Utopic. Trusty SRU pending.

Changed in juju-quickstart (Ubuntu):
status: New → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Please test proposed package

Hello Tugdual, or anyone else affected,

Accepted juju-quickstart into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju-quickstart/1.3.1-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in juju-quickstart (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Jay R. Wren (evarlast) wrote :

I cannot reproduce using local. It would have been worth noting that this only effects openstack and ec2 providers.

Using the versions from trusty-proposed
 juju=1.18.4+dfsg-0ubuntu0.14.04.1
juju-quickstart=1.3.1-0ubuntu1.1

I can't verify because of SSL certificate validation errors.

juju bootstrap works and then juju-quickstart fails:

$ juju-quickstart
juju quickstart v1.3.1
bootstrapping the jrwren-aws environment (type: ec2)
reusing the already bootstrapped jrwren-aws environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://ec2-54-208-132-174.compute-1.amazonaws.com:17070
12:31:37 WARNING app@connect:300 Retrying: unable to connect to the Juju API server on wss://ec2-54-208-132-174.compute-1.amazonaws.com:17070: [Errno 1] _ssl.c:510: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

It retries a number of time before giving up.

Is this a new bug?

Revision history for this message
Jay R. Wren (evarlast) wrote :

Nevermind the above SSL error message. I had python-websocket installed from juju-stable ppa.

Testing without ppa package and with trusty and trusty-proposed packages works.

$ juju-quickstart
juju quickstart v1.3.1
bootstrapping the jrwren-aws environment (type: ec2)
reusing the already bootstrapped jrwren-aws environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://ec2-54-208-132-174.compute-1.amazonaws.com:17070
bootstrap node series: trusty
charm URL: cs:trusty/juju-gui-7
requesting juju-gui deployment
juju-gui deployment request accepted
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
juju-gui/0 placed on ec2-54-208-132-174.compute-1.amazonaws.com
juju-gui/0 deployment is pending
machine 0 is started
juju-gui/0 is installed
juju-gui/0 is ready on machine 0

Juju GUI URL: https://ec2-54-208-132-174.compute-1.amazonaws.com
password: ***

connecting to the Juju GUI server
done!

Run "juju quickstart -e jrwren-aws" again if you want
to reopen and log in to the GUI browser later.
Run "juju quickstart -i" if you want to manage
or bootstrap your Juju environments using the
interactive session.
Run "juju destroy-environment jrwren-aws [-y]"
to destroy the environment you just bootstrapped.

tagging verifiation-done

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package juju-quickstart - 1.3.1-0ubuntu1.1

---------------
juju-quickstart (1.3.1-0ubuntu1.1) trusty; urgency=medium

  * Cherry-pick bugfixes from 1.3.2:
    - Make control bucket optional (LP: #1309678).
    - Support Trusty environments (LP: #1306537).
    - Check unicode support (LP: #1311321).
 -- Robie Basak <email address hidden> Wed, 02 Jul 2014 16:47:16 +0000

Changed in juju-quickstart (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for juju-quickstart has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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