Hi,
I noticed that for configuration status agents are always shown in error state regardless of their actual state.
On the Agents tab for a build configuration it shows two of our three agents, both with the exclamation marks stating that "Agents version does not match the server".
However in agent view of the administration interface our 3 agents are all shown as normal condition.
Hi Olli,
Is it affecting your ability to start a build or is it just a weird UI bug?
The data used to populate that tab in the first picture is taken from the agent compatibility cache and only updated when an agent is authorized/registered (and had a property change) or if a configuration is saved/deleted. If none of those happened then you’re probably getting old values. The data you see in the second picture you’ve attached is taken straight from the database. Do you know if de-authorizing then re-authorizing the agent fixes the error states you see in the first picture?
This appears to be limited to UI. Builds are working, and interestingly the agent where this particular build is always allocated is not listed in the configuration agent status.
Deauthorizing agent and reauthorizing does not appear to affect the listing.
Looks like it's stale data in the cache. I've made a change so the compatibility cache gets updated whenever an agent changes version. (Should be in the next build)