| Saving configuration changes on some agents* results in config-history being updated for a different node. IE making changes to labels for Agent A, press save, the config-history is updated for Agent B, with the current configuration from Agent B. The history.xml file shows that I was the user making the change to Agent B. If I make another change to Slave A and save, Agent C config-history is updated with current configuration from Agent C. To be clear:
- Current agent config.xml files are not altered in any unintended way, only the config-history files
- When saving the agent configuration, the agent configuration that is actually saved is incrementing alphabetically.
- The above problem is happening on every save of the agents configuration. definite and repeatable
Further:
The above problem seems to be causing an undesired effect in leaving the agent in a disconnected state. However, this is not repeatable.
The workaround is to re-save the configuration. Which then resumes connectivity between agent and master. * some in this case is 6 windows slaves (out of 246 mixed linux and windows slaves currently connected to master), the 6 agents aren't named sequentially and weren't connected to master at the same time |
