https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39314
Bug ID: 39314
Summary: RabbitMQ can't upgrade from 3.x to 4.x without running
a data migration on 3.13
Change sponsored?: ---
Product: Koha
Version: Main
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P5 - low
Component: Installation and upgrade (command-line installer)
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
Reported to Debian as it affects their next release which will do a jump from
3.10 to 4.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165#10
Which can't work: https://www.rabbitmq.com/docs/upgrade
«You can only upgrade to RabbitMQ 4.0 from RabbitMQ 3.13.»
«stable feature flags have to be enabled before the upgrade. The upgrade
will fail if you miss this step.»
See there more more details.
-----
For us: is there still data in RabbitMQ when stopping a Koha instance and
upgrading it? I recall reading that the DB was basically mirroring the message
queue data during a discussion about the actual need for a dedicated message
queue. Does it mean the koha-common package can wipe the RabbitMQ data which
will allow it to start without issue?
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
