Actions
Bug #9415
closedUser story #1808: Add an Audit mode to Rudder: only check properties, no modification on nodes
Nodes have several open nodeconfigurations
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Compliance & node report
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
On my test machine, I get to the situation where nodes have several opened expected node configurations:
rudder=> select nodeid, nodeconfigid, begindate, enddate from nodeconfigurations where nodeid = '00000010-55a2-4b97-8529-5154cbb63a18' and enddate is null; nodeid | nodeconfigid | begindate | enddate --------------------------------------+--------------+----------------------------+--------- 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:16:35.582+02 | 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:16:41.431+02 | 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:20:07.635+02 | 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:27:41.337+02 | 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:04:54.63+02 | 00000010-55a2-4b97-8529-5154cbb63a18 | 4f920c3b | 2016-10-18 03:05:32.522+02 |
It does not seem to lead to user viewable error, but it means that something is broken in the logic which update node configurations.
Actions