proposed origin does not work with local provider
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Undecided
|
Clint Byrum | ||
juju (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Test Case]
1. install juju from precise-proposed
2. create a local environment in ~/.juju/
3. juju bootstrap -e local-env-name
4. juju deploy -e local-env-name wordpress
- broken version will fail during the master customize step because of invalid origin
- fixed will succeed and produce a container with proposed enabled.
[Regression Potential]
This code is only used in conjunction with setting alternative origins in the local provider, so the others (distro, ppa, and a bzr branch) should be tested.
-------
The recent changed to add 'juju-origin: proposed' works fine for ec2, but with the local provider there is a syntax error in the 'juju-create' script:
elif [ $JUJU_ORIGIN = "proposed"]; then
Shell silently skips this and the origin is rejected as invalid. There should be a space between " and ]
Changed in juju: | |
milestone: | none → galapagos |
status: | New → Fix Released |
assignee: | nobody → Clint Byrum (clint-fewbar) |
Changed in juju (Ubuntu): | |
status: | New → Triaged |
Changed in juju (Ubuntu Precise): | |
status: | New → Triaged |
description: | updated |
Changed in juju (Ubuntu): | |
status: | Fix Committed → Fix Released |
r541 released to Quantal, marking Fix Released