New peer relations not created when upgrading charms

Bug #1175958 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Triaged
Low
Unassigned
juju (Ubuntu)
New
High
Unassigned

Bug Description

For the OpenStack HA work that we completed this cycle, we introduced peer relations to most charms to support clustering/scale-out features.

Upgrading from the previous version of the charms (keystone for example) does not error, but new peer relations are not created; this blocks upgrading and then clustering openstack deployments built on the current charm set.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: juju 0.7-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Fri May 3 09:54:37 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-04-23 (9 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: juju
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
James Page (james-page) wrote :
Robie Basak (racb)
Changed in juju (Ubuntu):
importance: Undecided → High
Curtis Hovey (sinzui)
Changed in juju:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.