Issue
I upgraded my CloudBees CI instance from 2.462.3.3 to 2.479.1.4, and when starting up, the UI only presented the logs below. In the startup logs, I found the very same logs and many other exceptions warning the startup process has failed.
SEVERE hudson.util.BootFailure#publish: Failed to initialize Jenkins java.lang.NoSuchMethodError: ‘boolean hudson.model.Computer.isMasterComputer()’ at PluginClassLoader for cloudbees-replication//com.cloudbees.jenkins.plugins.replication.ui.ReplicatedComputers.add(ReplicatedComputers.java:87) at PluginClassLoader for cloudbees-replication//com.cloudbees.jenkins.plugins.replication.ui.ReplicatedComputers$ComputerListenerImpl.onOnline(ReplicatedComputers.java:566) at jenkins.model.Jenkins.<init>(Jenkins.java:1056) at hudson.model.Hudson.<init>(Hudson.java:102) at hudson.model.Hudson.<init>(Hudson.java:87) at hudson.WebAppMain$3.run(WebAppMain.java:249) Caused: hudson.util.HudsonFailedToLoad at hudson.WebAppMain$3.run(WebAppMain.java:263) INFO hudson.lifecycle.Lifecycle#onStatusUpdate: Stopping Jenkins
Resolution
The cause for you to experience this error is related to the fact that in Beekeper configuration, the option Allow automatic upgrades of plugins on restart
was disabled. While generally, this poses some risks as detailed in our documentation, in this version and due to a breaking change in the cloudbees-replication
plugin, it can cause the behavior described above that can be fixed following the steps below.
-
Stop CloudBees CI.
-
Navigate in the filesystem under
$JENKINS_HOME/plugins
and remove the filecloudbees-replication.jpi
. -
Start CloudBees CI.
-
Navigate under
Manage Jenkins → Beekeeper Upgrade Assistant → Cap Configuration tab
and enable the checkboxAllow automatic upgrades of plugins on restart
to avoid similar failures in the future with any CAP plugin. -
Install the
cloudbees-replication
plugin once again if you are interested in using HA/HS.