-
Notifications
You must be signed in to change notification settings - Fork 30
agents with conflicting group membership #143
Comments
Yes, this isn't ideal behavior. I think it's a bug worth looking into, and I gave this the feature request label to also consider multi-group membership, as that's not the current design. In fact, I was considering hierarchical membership before, but that was put on the back burner. Thanks for reporting this! |
You bet. I'm just discovering this tool, and i expect I will have many more FR/Bug reports :) Thank you for building this framework, it does (i believe) exactly what i needed with out needing to build the hard part! |
@Mierdin I am trying to setup todd project on Centos 7. I configured todd agent and todd server. But when i am trying to access todd agents i am getting the below error. Could you please help. docker run --rm toddproject/todd todd agents Todd Server Log: Todd Agent logs: |
Looks like agents that match the criteria for multiple groups (one by subnet, the other by name) will flap between those groups.
You can see below the agent flip-flops between the groups "poc" and "poc2"
Fix: Preferring a most specific match over a least specific, where hostname is preferred over all. In the case of an exact match conflict (like hostnames in two groups), prefer not changing group membership, requiring the admin to remediate.
Feature Request: Multi-group membership :)
The text was updated successfully, but these errors were encountered: