Public bug reported:
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
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected regression-release saucy
** Tags added: apport-collected saucy
** Description changed:
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.
+ 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.
+ ---
+ 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
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1200878
Title:
Upgrade breaks existing pyjuju deployment
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1200878/+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
