Agent: Not yet assigned (ip:Unknown)

[Jeff Beard]

Hi folks,

I'm doing a POC with GO CD to compare it go our existing Jenkins infrastructure. I've been able to install it with the agent on the same host as the server but the agent I installed on a separate host while visible in the "Agents" view, doesn't get used by any pipelines. If I look at an individual pipeline job the "Agent" field has this value: Not yet assigned (ip:Unknown) and the pipeline remains in a running state. (Note, both hosts are EC2 instances with appropriately configured security groups.)

When I look at the log files on both sides when the agent starts I can see that it connects to the server and gets a "cookie".

I've also assigned resources to the agent and to the jobs in my test pipeline to no avail. It only works with the agent on the same host as the server and it does so without any interventions, as expected.

Does anyone have any advice about what to look at next?


Thanks,

Jeff

[Md. Ali Ejaz]

Hi Jeff,

For security reasons, agents pinging from a separate host machine than that on which server is installed, goes into pending state. The user has to enable this pending agent for it to start picking up jobs. 

The pending agents could be enabled from the Agents tab, where the user has to select the agent in question and enable it.

Let me know if this is the issue. If not, i think it would require more details/logs for investigation. 

Regards,

Ali

--
You received this message because you are subscribed to the Google Groups "go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Beard]

Hi Ali,

Thanks for your response.

I'm sorry I didn't mention it to begin with but yes, I've made sure that all the agents are enabled.

What events should I look for in the logs? As I mentioned, when I start the agent I only see the initial connection logged on both sides.


Thanks,

Jeff

[Md. Ali Ejaz]

Hi Jeff,

Agent field as 'Not yet assigned (ip:Unknown)' for a scheduled pipeline's job means there is no compatible agent for the given job. This could happen due to the following reasons:

1. Agent is not enabled and not in idle state (as i have mentioned before)
   
2. The pipeline is in an environment which doesn't have any agent to run that job.
   
3. The job resources don't match with the agent resources

If none of the above is the scenario in your case, i would need to have a look at the config, go-server log, go-agent log and any stderr logs on the agent (the agent on which this is being observed). You can mask any sensitive data from the config. For details about these file locations please refer - http://www.thoughtworks.com/products/docs/go/current/help/installing_go_server.html#location_of_files and http://www.thoughtworks.com/products/docs/go/current/help/installing_go_agent.html

PS: I'm assuming you have opened the ports 8153 and 8154 on the server machine.

Regards,

Ali

[Md. Ali Ejaz]

Just a small correction - what i meant by "there is no compatible agent for the given job" is "there is no compatible agent available for the given job"

There might be an agent assigned with correct resource or in correct environment but for some reason is not in idle state to pick up the job.

[Jeff Beard]

So it looks like I had an environment assigned to the remote agent that did not match configuration in the Job. I did have a resource assigned to the agent and the job. So I removed that environment from the agent and the next execution was performed on the remote agent.

Thanks for your help Ali.


Regards,

Jeff