From 936d1a10f5a842797f17e70899a1481b378b99c8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?P=C3=A9ter=20G=C3=B6m=C3=B6ri?= Date: Mon, 30 Sep 2024 01:01:52 +0200 Subject: [PATCH] Don't start invalid but enabled plugins at startup For example during the startup after RabbitMQ was upgraded but an enabled community plugin wasn't, and the plugin's broker version requirement isn't met any more, RabbitMQ still started the plugin after logging an error. (cherry picked from commit 2194822b3618ea7291517bcc29ecf36a359883f7) --- deps/rabbit/src/rabbit_plugins.erl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deps/rabbit/src/rabbit_plugins.erl b/deps/rabbit/src/rabbit_plugins.erl index 959a1a6de7cf..228c04bc2086 100644 --- a/deps/rabbit/src/rabbit_plugins.erl +++ b/deps/rabbit/src/rabbit_plugins.erl @@ -265,7 +265,7 @@ prepare_plugins(Enabled) -> [ExpandDir, E2]}}) end, [prepare_plugin(Plugin, ExpandDir) || Plugin <- ValidPlugins], - Wanted. + [P#plugin.name || P <- ValidPlugins]. maybe_warn_about_invalid_plugins([]) -> ok;