You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is more a feature request than a bug in my opinion 0:)
This will effectively change the way we apply the rules to nodes: send the rules to the nodes when they connect to the GUI, instead of being the nodes who send the rules to the GUI.
This behaviour is like it is, because we didn't have a way to store rules on the GUI, it was save on memory only, so the rules were only persistant on the nodes. But since some versions ago we can save rules to a DB on disk,
There's a benefit of adding this new working mode that I already thought some time ago: nodes could work without rules on disk, only on memory, which would make it harder for someone to know what's allowed or denied.
gustavo-iniguez-goya
changed the title
[Bug] Rules Not Applied To New Nodes
[Bug] Rules not applied to new nodes when they are not connected to the GUI
Aug 2, 2023
Perhaps having a two way sync with the last updated time setting the priority and all rules stored in a db at both ends. Or if the db was small enough you could sink the hole db.
This would also give more redundancy if the ui was unavailable but, having the rules in memory does sound good but how stable would it be if the ui was not available especially if a node rebooted.
Describe the bug
I have created some rules that are needed for all nodes but, when a new one is added or comes online these rules are not applied.
I have selected apply to all nodes and it works for the ones that are connected at that time but, no others which makes a lot more work.
Include the following information:
To Reproduce
Create and apply rule, then add new node or switch old one on.
Steps to reproduce the behavior:
Post error logs:
No related errors found
The text was updated successfully, but these errors were encountered: