-
Bug
-
Resolution: Fixed
-
Low
-
None
-
5.6
-
None
CONF-29513 tried to stop the plugin framework from starting on boot if the user is trying to migrate a cluster to a standalone instance or vice versa.
However, the implementation now means that we log in every instance where we're running a migration, we silently and accidentally start the plugin framework. And in every instance apart from a migrating instance that we're running a migration, we log "Confluence is being migrated. Not starting full plugin system." (which is a lie, because we do go ahead and start it).
At first glance it seems to be a small bug, shouldn't be too hard to fix.