Rebuilding a VM running bamboo agent and retaining UUID

[darren brewerton]

Hi,

Is it possible to restore a bamboo agent configuration and avoid having to manually approve a new UUID if the hosting virtual machine is re-created?

I have bamboo agents running as a systemd services. They are registered running OK after the initial manual agent approval. 

On occasion I need to destroy and recreate the VMs with new base images.

I have to reinstall the bamboo agent at the point the VM is created. The systemd service generates a new UUID and requests that the agent is approved.

If I then restore the original xml configuration file with the original Agent ID and UUID and restart the service the bamboo agent service doesn't read the config file.

Each time the service is stopped/started another temp-UUID is generated for registration.

Many thanks in advance. 

[Eduardo Alvarenga · Accepted solution]

Hello @darren brewerton,

Welcome to Atlassian Community!

If your Agent is launched via its startup script via <bamboo-agent-home>/bin/bamboo-agent.sh, it will load the <bamboo-agent-home>/bamboo-agent.cfg.xml properties file and connect using the provided UUID settings when connecting to the Server. If you still see an approval message, that means Bamboo is not loading or is replacing the file.

Is it possible that you are running the Installer jar package and expecting it to use the restored configuration file? If that's the case, you will have to:

• Install the Agent using the provider Jar package
• Stop the installer after it is "waiting for approval" message
• Replace the configuration files
• Start the Agent via <bamboo-agent-home>/bin/bamboo-agent.sh start

It would be best to consider installing the Agent by adding the extra install flag. That will instruct the installer to only place the files and not start the service. That allows you to replace the configuration files before starting the service for the first time. Check this documentation for more details:

• Additional remote agent options -- Expand Running the remote Agent with different start-up commands for more details

Here's a KB that shows how a Bamboo service needs to be configured via Systemd:

• Running Bamboo as a Linux service -- Make sure to expand the Systemd Service Configuration

Sincerely,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

[darren brewerton]

Much appreciated. I shall try your suggestions.