KBEC-00435 - Conversion from Concurrent Host to Registered Hosts

Article ID:360035667271
1 minute readKnowledge base

Problem

When a Concurrent License model is being changed to a Registered Host model, the customer may sometimes face the following error message upon License import when a larger (>200) number of resources are involved.

Solution

  • You should file a Support ticket to work with the Support team before attempting such a conversion directly.

  • A temporary mixed mode license will be provided. Named: "<org-date>-Temp-Conc-Reg.txt"

    • This license needs to be applied first to allow the next set of changes to be effective.

Method 1 - "modify_all_resources_hostType.sh"

  • Attached is a script that can run the modifyResource commands.

  • Usage

    • To make all resources REGISTERED run:

--------------------------------------------------------

./modify_all_resources_hostType.sh YOUR_COMMANDER_SERVER_NAME USERNAME REGISTERED

  • You will be prompted for Password

  • Wait for the script to complete

  • We can now apply the actual production license delivered to you, which will enable registered hosts.

Method 2 - Create your own script

  • Run the following SQL query on the Database

------------------------------------------------------------------------------------------------

select 'ectool modifyResource "' + r.name + '" --hostType REGISTERED' as ectool_cmds from ec_agent a , ec_resource r where a.id = r.agent_id;

The above query will only generate a list of ectool commands that will need to be run on the server after the application of the Mixed license.

  • To run the commands,

    • set up a Shell script with all the commands

    • Establish an ectool session on the command line

    • Execute the shell script

  • This will convert all the hosts to "registered" type

  • We can now apply the actual production license delivered to you, which will enable registered hosts.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.