Upgrade breaks existing pyjuju deployment

[Colin Watson]

A recent saucy system upgrade replaced pyjuju with juju-core. Now my existing deployment breaks as follows:

  $ juju status
  error: no CA certificate in environment configuration

No indication of what I'm supposed to do to fix this. Perhaps bug 1178314 is related, but I'm not sure.

Breaking existing deployments is surely unacceptable in a system upgrade. If this is a general problem and not specific to my deployment (which has been running for a few months, in Canonistack), then pyjuju should be restored until the upgrade experience is smooth.

(Fortunately, as I've discovered, /usr/lib/juju-0.7/bin/juju still works. This still seems rather non-obvious and suboptimal, though.)

== Regression details ==
Discovered in version: 1.11.2-0ubuntu1
Last known good version: 0.7-0ubuntu1
---
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 13.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-03-01 (133 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
MarkForUpload: True
Package: juju-core 1.11.2-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
Tags: saucy
Uname: Linux 3.10.0-2-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sbuild sudo uml-net

[Colin Watson (cjwatson)]

apport information

[Colin Watson (cjwatson)]

apport information

[John A Meinel (jameinel)]

I don't think this is strictly a bug in 'juju-core', more of a bug in the packaging. (Namely saucy has a package named "juju" which is a meta package that installs juju-core, while IIRC python-juju is no longer available on Saucy.)

If this was just 'apt-get upgrade' I would probably agree it shouldn't break things. If it is "apt-get dist-upgrade" then it isn't terrible.

The one thing we could consider is that "juju status" with juju-core could notice the environment is python-juju and fail with a nicer error.

Unfortunately the new requirement of a certificate means we don't even get far enough to read the bootstrap-verify file in provider storage.

[James Page (james-page)]

As there is still no upgrade path for environments created with py-juju to juju-core, I'm going to re-introduce the juju-0.7 package to saucy so we don't shoot all the existing juju environments that are already in use.

juju-core will still be the default juju implementation for saucy; however switching to the python implementation should be supported to allow people time to switch over prior to 14.04 when I would like to drop py-juju.

[Launchpad Janitor (janitor)]

This bug was fixed in the package juju - 0.7-0ubuntu2

---------------
juju (0.7-0ubuntu2) saucy; urgency=low

  * Re-introduce juju 0.7 package to saucy to support use with pre
    juju 1.11 environments (LP: #1200878):
    - d/control: Drop juju package; this is now owned by juju-core.
  * d/patches/juju-0.7-head.patch: Resync 0.7 release with head of
    upstream 0.7 branch.
  * d/patches/workaround-lxc-python-env.patch: Dropped, included in
    resync with upstream 0.7 branch.
  * d/rules,juju.docs->juju.docs.in: Put documentation into the juju-0.7
    package.
 -- James Page <email address hidden> Fri, 23 Aug 2013 12:07:03 +0100

[William Reade (fwereade)]

Closing in juju-core: lp:1220260 should cover what can be done to resolve it.

[Curtis Hovey (sinzui)]

I marked this as wont fix because this this was a packaging bug that was resolved downstream. Development releases do not support alternatives yet, we are tracking this in bug 1185496.