Possible bug failing to find a compatible agent temporarily?
Hiya,
we are using Team City Enterprise 7.0 (build 21241).
We have 10 agents, with only one of them having the necessary software to run Config "Build X".
One of our users ran a build that triggered about 20 configs, and one of them was "Build X".
All his configs succeeded, but the one running "Build X" never started, and when looking in the job queue, in the "Can run on" column, the job displays "No Agents".
This is odd because about 5 minutes later the same person triggered the same set of configs, and the new (but identical) job was picked up correctly by the compatible machine.
Also, if anyone now clicks on the "No Agents" message, Team City takes him to the page displaying the one compatible agent.
I think this is a bug, have you ever encountered this?
Cheers,
Simona
Please sign in to leave a comment.
Hi Simona
Please post teamcity-server.log where this issue is reproduced.
Thanks
Hi Simona,
What is the content of the poup over build's extimate in the queue?
Do you use snapshot dependencies with "run on the same agent" option?
Were any custom paramters specified (e.g. in custom run build dialog), when the build hanging in the queue was triggered?
Hi Yegor,
What is the content of the poup over build's extimate in the queue?
Unfortunately I don't have a case of this bug right now in the queue, so I can't check.
If you can suggest a way for me to check this from the interface somehow, please let me know (I can see the job in question in Team City, and click on it, but I can't see any useful info on it).
Do you use snapshot dependencies with "run on the same agent" option?
The job in question has no dependencies of any kind.
There is a job with a snapshot dependency further in the build chain from this one, but it's not using the "run on the same agent" option.
I believe we don't use this option anywhere in our jobs (but I'm not 100% sure, definitely not in this job).
Were any custom paramters specified (e.g. in custom run build dialog), when the build hanging in the queue was triggered?
The builds that have been causing this (2 so far) were remote runs run from the Visual Studio Team City Add In.
Both users just run them with the default values, they don't think they changed anything.
I'll make sure to check the popup over build estimate if this happens again.
I'm attaching what we could see at the point of failure (I forgot I had this screenshot).
Upon clicking on the "No agents" message you'd be taken to the page displaying one agent available.
I hope this helps
Cheers,
Simona
Attachment(s):
TCNoAgents.jpg
Hi Simona,
The content of the popup over build estimate should clarify the case a bit.
So far I can see only one case when this can happen: when a user specified custom build parameter on triggering a build (on triggering remote run in IDE) with a reference to an undefined parameter.
This is "as designed" case, but so far there is no easy way to tell this case from others from TeamCity web UI.
This issue is also described in TW-21177.
Hi Yegor,
can you explain a bit further what you mean by "undefined parameter"? I don't understand what you mean :)
The config we are seeing this on indeed needs a number of parameters, which are inherited from a template, and set in the config itself.
I can't think of how a remote run would change the fact the parameters are set correctly (and the config builds correctly 99.9% of the time).
The other things that make me think the diagnose might be incorrect are:
- this has happened only twice, and we have been doing hundred of remote runs (all from VS) on that config.
- this config is not called directly, but only by running a parent config that's dependent on it
- there are two "similar" configs (inheriting from the same template) that are called by the same parent config, and only one of the two has been observed to have this problem
- the same config will succeed immediately after if the same person does another remote run.
Other hints that this might be a very rare bug due to a low number of machines able to run a job (two) might be that this hasn't happened since we added a third machine able to run this type of config (this happened twice when we had only two).
I'll still look out for repros and that popup insight, but from how you describe the "expected behaviour" case, I suspect this isn't it.
Cheers,
Simona
reference to an "undefined parameter" is a reference to a parameter which is not defined.
e.g. is a user open custom run build dialog and adds new parameter with value %unknown_parameter%, this would be the case.
However, based on
> this config is not called directly, but only by running a parent config that's dependent on it
this is probably not the case.
If you happen to see this again, we would appreciate details of all the popups of this build int he queue.
But why is this agent listed in the list of compatible agents?
And how to determine which parameter is undefined?
Looks like I have same issue. Agent is authorized and enabled and according to the "Compatible Agents" tab is compatible to build project. But "Build Queue" tab informs that there are no compatible agents to build project.