|
|
|
[
Permlink
| « Hide
]
Robin Shen [14/Sep/22 10:57 PM]
OS is not an issue. When snapshot is being restore, please check server log to see if agent is timedout. Only in that case, reconneted agent will reload the attributes.
I changed 'Agent Timeout' setting to shorter time instead of making the reversion to take longer and then reverted the agents. I still received the the same issue. The OS of these agents Windows 11. Do you think the OS causes the issue?
I will do as your suggestion and let you know. Thanks!
Seems that in your case, your agent reconnects shortly after a snapshot restore, and QB actually does not detect a connection loss. You will have to add some logic to make snapshot restore a bit longer to wait for agent to be timedout. In that case, QB server console will display something like:
Active build agent 'agentmachine:8811' timed out, removing.. Otherwise, everything seems fine to QB server, and there is no reason to reload attributes from time to time. Is it possible if QB re-syncs the attributes every re-connection? I think that is helpful and keeps the attributes in sync.
QB only thinks that the connection is temporarily down, and if it reconnects, it thinks network comes back, but in this case there is no reason to re-sync the attributes.
Thanks, again!
Looks like QB updates agent's attributes after the agent is re-started. I am curious that when I revert the machine/agent, QB also loses the connection to the agent and reconnects to it successfully. Why the attributes are not updated? Without restarting the agent, QB has no chance to know the agent attribute is updated.
Thank you for prompt response. It works with stopping and then starting the agent as your suggestion. However, it may not work for my test automation, since I cannot revert and stop/start agent in one automation and have many agents and tests that are running in parallel.
This is odd. Please stop the agent, waiting for it to be removed from active agent list, and start again to see it works.
I rebooted the agent, but the attributes were still not synchronized.
Please restart agent after reversion to see if attributes can be synchronized.
|