** Description changed: + [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 + elif [ $JUJU_ORIGIN = "proposed"]; then Shell silently skips this and the origin is rejected as invalid. There should be a space between " and ]
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1007657 Title: proposed origin does not work with local provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1007657/+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
