+++ This bug was initially created as a clone of Bug #1755152 +++ Description of problem: Issue in rabbitmq-plugins in rabbitmq-server-3.7.16-1.fc30.x86_64 ``` [vagrant@vanilla-f30 ~]$ sudo rabbitmq-plugins enable rabbitmq_management Enabling plugins on node rabbit@vanilla-f30: rabbitmq_management The following plugins have been configured: rabbitmq_management rabbitmq_management_agent rabbitmq_web_dispatch Applying plugin configuration to rabbit@vanilla-f30... The following plugins have been enabled: rabbitmq_management rabbitmq_management_agent rabbitmq_web_dispatch set 3 plugins. Offline change; changes will take effect at broker restart. chown: invalid user: ‘@RABBITMQ_USER@:@RABBITMQ_GROUP@’ ``` It looks like this upstream commit to the specfile [1] wasn't properly synced downstream into [2] because there is no sed command to replace `@RABBITMQ_USER@:@RABBITMQ_GROUP@` in our version of the spec file. [1] https://github.com/rabbitmq/rabbitmq-server-release/commit/7d43d3538bbafb12b7083ea2f75ac472d24167ad [2] https://src.fedoraproject.org/rpms/rabbitmq-server/blob/master/f/rabbitmq-server.spec
(In reply to Mauro Oddi from comment #0) > Issue in rabbitmq-plugins in rabbitmq-server-3.7.16-1.fc30.x86_64 Please verify this is indeed the installed version, that is a Fedora build
The text in the description is from the Fedora bug he cloned. I imagine he's having the same problem but from a different build.
(In reply to Dusty Mabe from comment #3) > The text in the description is from the Fedora bug he cloned. I imagine he's > having the same problem but from a different build. Ah right, I completely missed that this was a clone.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:0553