Issue
-
We changed the Operations Center URL (for example after setting up HTTPS) and now Client controllers are disconnected
-
We changed the Operations Center URL (for example after setting up HTTPS) and now Client controllers log in link takes me to the old URL.
Resolution
The recommended approach is to release and reconnect the Client controller.
Pre-Requisite
-
If the Client controller is using Operations Center SSO, the disconnection will cause the Client controller to switch to the fallback Security Realm that should allow users to still be able to login. Please review Single sign-on fallback behavior to ensure that this is set up properly. Otherwise, the controller will not be accessible when disconnected and in that case security would need to be disabled temporarily (see How do I login to Jenkins when I locked myself out?) to reconnect the controller.
-
If the Operations Center URL was changed from
http
tohttps
, make sure that the Operations Center certificate is trusted by the Client controller. Otherwise, add the required certificate(s) to the Client controller’s truststore, see How to install a new SSL certificate on Traditional Platforms?
From the UI
This is the recommended approach:
-
[CJOC] Go to the Disconnect and Release the Client controller
page and -
[CJOC] Connect the Client controller (by either pushing connection details OR copy / pasting the connection details as documented in Setting up your new Client controller)
If Client controller is not accessible from the UI
In case you do not have access to the UI or if you cannot log in to the Client controller after disconnecting it, follow this approach:
-
[CJOC] Go to the Disconnect and Release the Client controller
page and -
[controller] Stop the Client controller
-
[controller] In the Client controller file system, delete:
-
$JENKINS_HOME/license.xml
-
$JENKINS_HOME/operations-center-cloud*
-
$JENKINS_HOME/operations-center-client*
-
$JENKINS_HOME/com.cloudbees.opscenter.client.plugin.OperationsCenterRootAction.xml
-
-
[controller] Disable security in the Client controller by editing
$JENKINS_HOME/config.xml
. Locate this line:<useSecurity>true</useSecurity>
and changing it to<useSecurity>false</useSecurity>
If using CasC for Controllers, CasC will need to be disabled temporarily. Remove the -Dcore.casc.config.bundle=…
argument. -
[controller] Start the Client controller
-
[CJOC] Connect the Client controller (by either pushing connection details OR copy / pasting the connection details as documented in Setting up your new Client controller)