Cloud Agent not not registering in the Correct Pool

Avatar
Jeff
Created

So I have an issue with Cloud Agents... I have a configured cloud agent that is not launching into the correct pool.

The cloud log shows the following.

[2019-11-12 17:57:50,779]   INFO [0 Flush Queue 1] - .instances.StartInstanceAction - Starting cloud instance: profile 'content-cloud-profile'{id=amazon-4, projectId=project44}, AmazonImageInstance{id=po-content-agent-01, amazonId=i-0c056aa188bb793b7}, hash=1L4voUfMmoMZ2i9JyMs7BiA8btkJPvZI, reason=Automatic start: Compatible with queued build Content / ODS - TestWiz / Enrollments(promotionId=6136)
[2019-11-12 17:57:50,779]   INFO [0 Flush Queue 1] - .server.impl.CloudEventsLogger - Cloud instance entered 'scheduled to start' state, profile 'content-cloud-profile'{id=amazon-4, projectId=project44}, Amazon Instance{instanceId=po-content-agent-01, imageId=po-content-agent-01, amazonImageId=i-0c056aa188bb793b7, amazonInstanceId=i-0c056aa188bb793b7, status: Scheduled to start}
[2019-11-12 17:57:50,779]   INFO [0 Flush Queue 1] - .server.impl.CloudEventsLogger - Cloud instance start succeeded: profile 'content-cloud-profile'{id=amazon-4, projectId=project44}, Amazon Instance{instanceId=po-content-agent-01, imageId=po-content-agent-01, amazonImageId=i-0c056aa188bb793b7, amazonInstanceId=i-0c056aa188bb793b7, status: Scheduled to start}
[2019-11-12 17:57:56,327]   INFO [uled executor 5] - .server.impl.CloudEventsLogger - Cloud instance entered 'starting' state, profile 'content-cloud-profile'{id=amazon-4, projectId=project44}, Amazon Instance{instanceId=po-content-agent-01, imageId=po-content-agent-01, amazonImageId=i-0c056aa188bb793b7, amazonInstanceId=i-0c056aa188bb793b7, status: Starting}
[2019-11-12 17:58:51,368]   INFO [uled executor 4] - .server.impl.CloudEventsLogger - Cloud instance entered 'running' state, profile 'content-cloud-profile'{id=amazon-4, projectId=project44}, Amazon Instance{instanceId=po-content-agent-01, imageId=po-content-agent-01, amazonImageId=i-0c056aa188bb793b7, amazonInstanceId=i-0c056aa188bb793b7, status: Running}

This shows the instance starting and associated with the correct pool.

However, when looking at the Agents page the agent shows in the default pool despite it being configured to launch in the project pool and the cloud log showing it associate with the correct pull.

The agent is an instance based cloud agent rather than an AMI based cloud agent. Let me know what other information you need.

Also, I was required to authorize the agent before it would start working. I thought agents configured as Cloud Agents did not require this step. Please advise.

Thanks,

Jeff

Votes

0

Share

4 comments
Avatar
Jeff
Created

I think I fixed it by updating the EC2Config version.

0
Avatar
Jeff
Created

Per...

 

https://www.jetbrains.com/help/teamcity/setting-up-teamcity-for-amazon-ec2.html#SettingUpTeamCityforAmazonEC2-ImportantnoteforimagesbasedonWindowsServer2016image

0
Avatar
Jeff
Created

I would still like clarification on whether or not Instance based cloud agents should require authorization or not.

0
Avatar
Denis Lapuente
Created

Hi Jeff,

 

cloud agents should be automatically authorized if started via the cloud profile (that's what you mean with "instance-based" if I'm not mistaken). If you launch an image manually, then it will require authorization, as the server is not handling the lifecycle of the agent in that instance.

 

If you are experiencing that the images do not get authorized automatically, please send us your logs via the submit a request button on top of this page.

0

Please sign in to leave a comment.