No way to test proposed updates to juju
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
High
|
Kapil Thangavelu | ||
juju (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Kapil Thangavelu |
Bug Description
[Impact]
Users will not be able to test any proposed updates to juju in deployed nodes.
[Dev Fix]
Add a new origin "proposed" to that environments will enable the proposed pocket on deployed nodes.
[Stable Fix]
Backport of Dev Fix
[Test Case]
1. edit ~/.juju/
2. bootstrap said environment (juju bootstrap -e envname)
3. Verify that bootstrap node has proposed pocket enabled using 'juju ssh 0'. If there are proposed juju updates for that release, verify that juju was installed from proposed.
[Regression Potential]
Very Low. The fix just adds a new origin type, 'proposed', so the others are not really affected and the logic leading to all of the origin types is very straightforward. There is also very good test coverage of the affected code.
== Original Bug Description ==
juju-origin in environments.yaml needs to accept 'distro-proposed', or environments.yaml needs to accept some other option that will allow directing juju to install the version of juju from the -proposed pocket.
The simplest thing is to allow juju-origin to have the URL of a .deb.
This is currently blocking the ability to do an SRU for the bugs fixed in juju since the Ubuntu 11.10 release.
Related branches
- Clint Byrum (community): Approve
-
Diff: 199 lines (+69/-7)6 files modifiedjuju/lib/lxc/__init__.py (+1/-0)
juju/lib/lxc/data/juju-create (+7/-1)
juju/providers/common/cloudinit.py (+17/-6)
juju/providers/common/launch.py (+2/-0)
juju/providers/common/tests/data/cloud_init_proposed (+37/-0)
juju/providers/common/tests/test_cloudinit.py (+5/-0)
Changed in juju (Ubuntu Oneiric): | |
status: | New → Triaged |
Changed in juju (Ubuntu Precise): | |
status: | New → Triaged |
Changed in juju: | |
importance: | Undecided → High |
Changed in juju (Ubuntu Oneiric): | |
importance: | Undecided → High |
Changed in juju (Ubuntu Precise): | |
importance: | Undecided → High |
Changed in juju: | |
milestone: | none → florence |
status: | New → Confirmed |
tags: | added: rls-mgr-p-tracking |
Changed in juju: | |
assignee: | nobody → Kapil Thangavelu (hazmat) |
status: | Confirmed → In Progress |
Changed in juju: | |
milestone: | florence → galapagos |
Changed in juju (Ubuntu Precise): | |
assignee: | nobody → Kapil Thangavelu (hazmat) |
milestone: | none → honolulu |
status: | Triaged → In Progress |
Changed in juju: | |
status: | In Progress → Fix Released |
description: | updated |
Changed in juju (Ubuntu Precise): | |
milestone: | honolulu → none |
Changed in juju (Ubuntu Precise): | |
milestone: | none → ubuntu-12.04.1 |
This bug was fixed in the package juju - 0.5+bzr538-0ubuntu1
--------------- 0ubuntu1) quantal; urgency=low
juju (0.5+bzr538-
* New upstream snapshot (LP: #993034, LP: #926550)
-- Clint Byrum <email address hidden> Tue, 29 May 2012 22:36:40 -0700