redhat-cop / redhat-cop/group-sync-operator
Error status code received from the API
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
Hello Team,
I have installed the group-sync operator in an ARO Cluster. But the configuration is still in LastReconcileCycleFailed A customer has reinstalled the Group Sync Operator, and while they have identified a possible cause of the issue, the error persists.
After reinstalling group-sync, they encountered the following logs:
INFO controllers.GroupSync Beginning Sync {"groupsync": "group-sync-operator/azure-groupsync", "Provider": "azure"}
1.7424798661324766e+09 ERROR syncer_azure Failed to get Group members for Group {"Group": "user", "Provider": "azure", "error": "error status code received from the API"}
Upon validation, the group did not exist in Azure AD. To test, they:
1. Created the group in Azure AD.
2. Added a member to it.
3. Updated the GroupSync YAML configuration to include it.
However, the issue persists, and the API error continues to appear.
Even after uninstalling and reinstalling the operator, the same error is logged, which suggests that the operator might be caching previous configurations. They are reviewing the provided documentation for alternative approaches but would appreciate any insights on what could be causing this behavior.
Has anyone encountered a similar issue where Group Sync Operator? Any guidance would be greatly appreciated.
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
Start with the syncer_azure log path and the GroupSync YAML configuration, then reproduce the API error against the Azure AD group described in the issue. Check the operator's group lookup and configuration behavior; done means identifying the cause of the persistent error and validating the resolution with a successful sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100