Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts

Bug #506985 reported by Tom Haddon
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rabbitmq-server (Ubuntu)
Fix Released
High
Unassigned
Lucid
Fix Released
High
Unassigned

Bug Description

Binary package hint: rabbitmq-server

Per http://pastebin.ubuntu.com/356068/, on upgrading from 1.54 -> 1.7.0, users and vhosts are wiped out. I checked in #rabbitmq on freenode, and the suggestion there was that this is a packaging bug.

Tags: patch
Revision history for this message
Mathias Gug (mathiaz) wrote : Re: [Bug 506985] [NEW] Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts

 importance high

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

Changed in rabbitmq-server (Ubuntu):
importance: Undecided → High
Revision history for this message
Soren Hansen (soren) wrote :

Release notes from 1.7.0:

   http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091007/3aaed239/attachment.txt

Quote:

  Upgrading
  =========
  The database schema has not changed since the 1.6.0 release, so user
  accounts, durable exchanges and queues, and persistent messages will
  all be retained during the upgrade.

  If, however, you are upgrading from a release prior to 1.6.0, when the
  RabbitMQ server detects the presence of an old database, it moves it
  to a backup location, creates a fresh, empty database, and logs a
  warning. If your RabbitMQ installation contains important data then we
  recommend you contact <email address hidden> for assistance with the
  upgrade.

Revision history for this message
Soren Hansen (soren) wrote :

In other words, this is expected, yet highly unfortunate behaviour.

We have a few options:

1. Version the binary packages and specify a Breaks: relationship between them.
2. Show a great big warning that this is going to happen.
3. Somehow pursuade upstream to provide a proper upgrade path.

Soren Hansen (soren)
Changed in rabbitmq-server (Ubuntu):
status: New → Confirmed
Revision history for this message
Soren Hansen (soren) wrote :

I'm leaning towards option 1, since this actually reflects reality. Any takers?

Revision history for this message
Elliot Murphy (statik) wrote : Re: [Bug 506985] Re: Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts

I can prepare a patch this weekend adding Breaks:

--
Elliot Murphy | https://launchpad.net/~statik/

On Jan 15, 2010 9:06 AM, "Soren Hansen" <email address hidden> wrote:

I'm leaning towards option 1, since this actually reflects reality. Any
takers?

-- Upgrade from rabbitmq-server 1.54 -> 1.7.0 wiped users and vhosts
https://bugs.launchpad.net/bu...

Revision history for this message
Elliot Murphy (statik) wrote :

I'm confused about how to do this, debian policy states that "A special exception is made for packages which declare that they break their own package name or a virtual package which they provide (see below): this does not count as a real breakage.". http://www.debian.org/doc/debian-policy/ch-relationships.html

I've tried adding a "Breaks: rabbitmq-server (<< 1.5.4-0)" and don't see any warning or complaint when trying to install with dpkg when 1.5.4 is currently installed.

I'm probably missing something simple, but google is not helping me tonight so I'm attaching the patch and will look for help on IRC sometime tomorrow.

Chuck Short (zulcss)
Changed in rabbitmq-server (Ubuntu):
milestone: none → ubuntu-10.04-beta-2
tags: added: patch
Revision history for this message
Soren Hansen (soren) wrote :

I also can't quite work out what the deal is with specifiying Breaks against oneself. What I meant in option 1) was to version the binaries (e.g. renaming it rabbitmq-server1.7) so that they're actual different packages in which case the inter-package relationships seem more sensible.

Revision history for this message
Chuck Short (zulcss) wrote :

Soren,

This appears to be taking a very large sledgehammer for a smallish problem. Maybe adding a note to the Debian.README and or release notes to tell the users that this going to happen.

chuck

Revision history for this message
Chuck Short (zulcss) wrote :

I was thinking about something like the following

Revision history for this message
Chuck Short (zulcss) wrote :

Scratch that, this would be a better idea.

Revision history for this message
Thierry Carrez (ttx) wrote :

Sounds good to me, since 1.5.4 -> 1.7.0 will not be hit by normal upgrade scenarios.

The message sounds wrong though:

Description: Upgrading from 1.5.4 and below.
 You are upgrading from a release prior to 1.7.2.

I suspect you want:

Description: Upgrading from 1.5.4 and below.
 You are upgrading from a release prior to 1.6.0.

Revision history for this message
Thierry Carrez (ttx) wrote :

Untargeting for beta2 since this is not a supported ({hardy,karmic} -> lucid) upgrade scenario.

Changed in rabbitmq-server (Ubuntu Lucid):
milestone: ubuntu-10.04-beta-2 → none
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package rabbitmq-server - 1.7.2-1ubuntu1

---------------
rabbitmq-server (1.7.2-1ubuntu1) lucid; urgency=low

  * debian/preinst, debian/rabbitmq-server.templates: Warn user about upgrading from a really old version.
    (LP: #506985)
  * debian/control: Update maintainer according to spec.
 -- Chuck Short <email address hidden> Tue, 30 Mar 2010 23:10:55 -0400

Changed in rabbitmq-server (Ubuntu Lucid):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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