How do I re-attach a Master to Operations Center when I cannot logon to the master?

Issue

A master shows as disconnected in Operations Center. The screen may look like below with the master shown with a red cross icon.

disconnect.png

When attempting to detach and re-attach the master you are unable to push the configuration as the master is requesting authentication, but you cannot logon as security has been previously managed via Operations Center.

 

Environment

  • CloudBees Jenkins Operations Center 1.6

*CloudBees Jenkins Enterprise

Resolution

You will need to temporarily disable security on the master and disconnect in from Operations Center.

Step1 - Shutdown the master

  • From the console, shut down the master

Step 2 - Erase security configuration

  • Locate the config.xml file in [$JENKINS_HOME]/
  • Replace this line:

<useSecurity>true</useSecurity>

with

`<useSecurity>false</useSecurity>`
  • Delete the following file:

         com.cloudbees.opscenter.client.plugin.OperationsCenterRootAction.xml

Step 3 - Restart the master

  • Start the master

Step 4 - Re-attach

You should then me able to push the configuration again from Operations Center

  1. Configure Client Master->…(save)->Connection details->Client master URL (Push configuration)

Please, use the push configuration option instead of using the copy/paste Connection details approach.

Additional information on setting up CloudBees Jenkins Operations Center for the first time and configuring it afterwards can be found here: Setup and configuring the initial instance..

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    Robert Hayosh

    I get this error message when clicking the link in this article:

     

    Unknown Host


    Description: Unable to locate the server named "operations-center.cloudbees.com" --- the server does not have a DNS entry. Perhaps there is a misspelling in the server name, or the server no longer exists. Double-check the name and try again.

  • 0
    Avatar
    Steven Christou

    Hello Robert,

    The link should now be fixed and point to the correct location. Thank you for reporting this!

Please sign in to leave a comment.