I am also affected. And was stopped nicely by the do-release-upgrade
command. Hopefully RabbitMQ can soon fix this issue, so I can upgrade my
Ubuntu Server to 24.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Not sure if this should be a new report or added to this one, so I'll
start here and create a new report if directed to.
I am trying to execute do-release-upgrade and I'm getting this error
message:
Currently, you have RabbitMQ server installed, which is not directly
upgradable to the newer v
** Changed in: ubuntu-release-upgrader (Ubuntu Oracular)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074309
Title:
upgrade 22.04 -> 24.04 won't start due to fe
** Merge proposal linked:
https://code.launchpad.net/~juliank/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/472685
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074309
Title:
upgr
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074
This bug was fixed in the package ubuntu-release-upgrader - 1:24.04.22
---
ubuntu-release-upgrader (1:24.04.22) noble; urgency=medium
[ Tobias Heider ]
* Fix typo in force_obsoletes. (LP: #2076913)
[ Nick Rosbrook ]
* DistUpgrade: handle cache key error when removing obsolete
Hi Hadmut, yes I agree. Unfortunately it's a bit easier to modify this
bug than the ubuntu release ugprade message, hence why the message in
the upgrader is so sparse. The hopeful plan is to have a nice wiki page
to redirect to.
I'm working on a good alternative upgrade path that we can rely on fo
Hi,
actually I do not have any problem to fix anymore since the workaround
procedure with podman described above totally solved my problem.
(Improvement: replace 127 with $(id -u rabbitmq) and 138 with $(id -g
rabbitmq)
But to test the bug fix I've setup a fresh 22.04 in LXD, installed
rabbit
The most recent upload contains a new quirk for an unrelated bug, and
fixes for another unrelated bug. The previous verification done with
1:24.04.21 stands.
** Tags removed: verification-needed verification-needed-noble
** Tags added: verification-done verification-done-noble
--
You received th
Hello Hadmut, or anyone else affected,
Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.22
in a few hours, and then in the -proposed repository.
Please help us by testing this
I verified the upgrade quirk using ubuntu-release-upgrader from noble-
proposed:
nr@six:~$ lxc launch ubuntu:jammy jammy
nr@six:~$ lxc exec jammy bash
root@jammy:~# apt install -y rabbitmq-server
[ ...SNIP... ]
root@jammy:~# do-release-upgrade --proposed
Checking for a new Ubuntu release
There is
Hello Hadmut, or anyone else affected,
Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.21
in a few hours, and then in the -proposed repository.
Please help us by testing this
There's another option, although an ugly one.
If it is too bulky to be supported in a clean way, and too incompatible
with Ubuntu's upgrade cycles, and if the problem with upgrading can't be
properly solved in the Ubuntu universe, it could simply be dropped from
Ubuntu (and Debian), and users be
Great points Hadmut.
It is unfortunate how far behind we are in versions. We follow debian
which hasn't been updated in a bit. I was thinking about updating the
package there, but I need to fix the fires here first (and if I update
debian to the latest without handling this bug's issue, I will bre
You're welcome. :-)
As I commented in #1, the upgrade using podman was working well for me,
but the question is, how long these docker images of old versions will
be available.
When creating an upgrade strategy, you also should take into
consideration, how long this upgrade should work, i.e. whet
** Description changed:
+ [Impact]
+
+ Upgrading systems with rabbitmq-server installed will leave the server
+ in a bad state because upgrading directly from the version in Jammy to
+ the version in Noble is not supported by upstream rabbitmq-server.
+
+ [Test Plan]
+
+ For now, we add an upgr
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2074309
Title:
upgrade 22.04 -> 24.04 won't start due to feature
Hadmut, thanks again for bringing this to our attention.
With 24.04.1 coming out soon we may expect more upgrades from Jammy ->
Noble. Therefore I am looking to block the upgrade (22.04 -> 24.04) if
rabbitmq-server is installed.
This is unfortunate, but I think is a fair to not make rabbitmq-serv
I just want to update on my upgrade test.
First and foremost - a direct upgrade from Jammy to Noble is not
possible.
It only is if you have it installed and have not used rabbitmq-server,
thus no metadata is made yet.
If you use the server in Jammy and then attempt to upgrade to Noble
right now
I added an ubuntu-release-upgrader task because we might consider
blocking the release upgrade there if the conditions for this bug are
found to be present.
Those conditions might be as simple as "is rabbitmq-server installed
(and running)?". Or perhaps a more generic one, carefully checking the
v
I made an upstream bug report directly asking for support doing these
major version hops[0].
[0] - https://github.com/rabbitmq/rabbitmq-server/discussions/11938
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
There is a github issue mentioning this[0]. There is potential plans to
improve feature flags[1], but they do not help us right now, and will
not help users that encounter this situation.
It seems the properly supported upgrade path is indeed installing 3.10
-> 3.11.
[0] - https://github.com/rabb
22 matches
Mail list logo
