EC2 Cloud Agent + Agent Push - Wrong IP on startup?

I have Team City configured to launch agents through EC2 and then install the agent on them through Agent Push.  The EC2 Instance is launched, and it shows up in the cloud agent tab, but if I log into the server the build agent is never installed.  I can then go to Agent Push and manually do an agent install on that server and it works fine.

The one thing I've noticed is that looking at the agent parameters for the cloud agent (cloud agent -> instance id-> agent parameters) it has the wrong address for ec2.public-ipv4

How is that value determined?  

-Lkb

4 comments
Comment actions Permalink

When you start an EC2 instance, it will show up on the cloud agents tab. This tab displayed started cloud instances, not agents. Agent Push installs buildAgent on particular host. But, if you use AMI images, the volume information (i.e. everything that has changed) goes away after instance is terminated.


Address for ec2.public-ipv4 is updated every time a new instance of the same type is started and agent connected (again, if you are using AMI images). The value displayed here is this value for the latest connected agent

0
Comment actions Permalink

That makes sense, so the ipv4 address there is actually just the last agent to successfully connect.

Any suggestions on how to troubleshoot the failure of the agent push?  Agent push works fine when i trigger it manually but is not happening when the cloud instance is started.

0
Comment actions Permalink

You can check teamcity-agentPush.log on server. Agent push might rely on some software that is absent on agent.

0
Comment actions Permalink

Did you find a solution to this issue?

0

Please sign in to leave a comment.