redhat-cop / redhat-cop/group-sync-operator
verbose/debug mode (unexpected pruning)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Hello All,
please is there a way to make the manager (container) to log outputs with more verbosity than by default?
I am facing an issue, that one of the groups synced gets sometimes auto pruned, even the respective AD group is existing and contains users.
The log then says the sync was completely successful. The (unexpected) group pruning is indicated as well.
Next scheduled/forced run recreates the group again.
Could the issue be caused by situation, that the group is found on AD, but the transfer of data for the group from AD then fails (eg nw issue) and having no data for group received that means pruning of the group by the operator?
- Group Sync Operator - 0.0.24
- LDAP
Many thanks for your advices
Kind regards,
Peter
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by finding the LDAP group synchronization and pruning entry points, then determine whether a failed group data transfer can be treated as an empty result. Done means the unexpected pruning behavior is reproduced and its handling or documentation is clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100