Find the answers to your Go questions, including FAQs, how-tos, tips and tricks

This is a public Discussion Area publicRSS

How To

Agents which are cloned from a virtual machine image...

How To posted July 22, 2009 by Qiao Liang 乔梁, last edited October 15, 2009 by Jez Humble , tagged agent, Installer, Scheduling, Server

1400 Views

Title:

Agents which are cloned from a virtual machine image conflict

Problem:

I have installed an agent on a virtual machine, and it worked fine with Cruise server.

However when I clone the VM image, both of the agents get confused, and a job can be building on both agents at the same time.

Solution Description:

The reason is that Cruise server identifies agents by a unique id (UUID) which is generated by the agent the first time it starts up.

If you clone an agent, the UUID is copied too. So both of the agents with same UUID talk to Cruise server, and the server becomes dysfunctional.

To resolve this issue, you just delete the file guid.txt under {agent_installation_folder}/config.

Then Cruise server will recognize it as a new agent, and you can approve it.

This issue will be fixed in a future version of Cruise.