Upgrade breaks existing pyjuju deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
High
|
Unassigned | ||
juju (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
juju-core (Ubuntu) |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
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/
== 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
PackageArchitec
ProcVersionSign
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
Related branches
Changed in juju-core (Ubuntu): | |
importance: | Undecided → High |
Changed in juju-core (Ubuntu): | |
status: | New → Triaged |
Changed in juju-core (Ubuntu): | |
importance: | High → Critical |
tags: | added: papercut |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Critical |
Changed in juju-core: | |
importance: | Critical → High |
apport information