proposed origin does not work with local provider

Bug #1007657 reported by Clint Byrum
10
This bug affects 1 person
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/environments.yaml, with juju-origin: proposed
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
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

r541 released to Quantal, marking Fix Released

Changed in juju (Ubuntu):
status: Triaged → Fix Released
description: updated
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Whoops, r542 has the actual fix.

Changed in juju (Ubuntu):
status: Fix Released → Triaged
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

r542 has been uploaded to Debian unstable. Just awaiting sync.

Changed in juju (Ubuntu):
status: Triaged → Fix Committed
Changed in juju (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Clint, or anyone else affected,

Accepted juju into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/juju/0.5+bzr531-0ubuntu1.2 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 change the bug tag from verification-needed to verification-done. If it does not, 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 (Ubuntu Precise):
status: Triaged → Fix Committed
tags: added: verification-needed
Revision history for this message
James Page (james-page) wrote :

Confirmed fixed with 0ubuntu1.2:

ubuntu@ubuntu-local-wordpress-0:~$ cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu precise main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu precise-security main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu/ precise-proposed main universe
ubuntu@ubuntu-local-wordpress-0:~$ apt-cache policy juju
juju:
  Installed: 0.5+bzr531-0ubuntu1.2
  Candidate: 0.5+bzr531-0ubuntu1.2
  Version table:
 *** 0.5+bzr531-0ubuntu1.2 0
        500 http://archive.ubuntu.com/ubuntu/ precise-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status
     0.5+bzr531-0ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages

Verification 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 - 0.5+bzr531-0ubuntu1.2

---------------
juju (0.5+bzr531-0ubuntu1.2) precise-proposed; urgency=low

  * d/p/upstream-541-542.patch: fix shell script to make proposed work
    for local provider. (LP: #1007657)

juju (0.5+bzr531-0ubuntu1.1) precise-proposed; urgency=low

  * d/p/upstream-532.patch: use proper whitespace separation in
    relation-ids. (LP: #988065)
  * d/p/upstream-533.patch: workaround to suppress Zookeeper logging
    which goes out of control in local provider on Reboot.(LP: #958312)
  * d/p/upstream-534.patch: fix to stop juju-log and relation-set commands
    outputting "{}" to stdout, which can break some programs and makes it
    difficult to use them in a debug-hooks session. (LP: #915506)
  * d/p/upstream-537.patch: make HTTPS apt sources usable inside local
    provider. (LP: #993034)
  * d/p/upstream-538.patch: Add support to install juju from proposed
    pocket to test proposed SRU's. (LP: #926550)
 -- Clint Byrum <email address hidden> Mon, 18 Jun 2012 14:00:56 -0700

Changed in juju (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers