redhat-cop / redhat-cop/group-sync-operator
Unable to sync Azure groups after updating Operator to v0.0.23
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 132
- Forks
- 71
- PR merge metrics
- No merged PRs in 30d
Description
I1222 16:54:59.494394 1 request.go:601] Waited for 1.040893871s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/network.openshift.io/v1?timeout=32s
1.6717281019386058e+09 INFO controller-runtime.metrics Metrics server is starting to listen {"addr": "127.0.0.1:8080"}
1.671728101939002e+09 INFO setup starting manager
1.6717281019395614e+09 INFO Starting server {"path": "/metrics", "kind": "metrics", "addr": "127.0.0.1:8080"}
I1222 16:55:01.939681 1 leaderelection.go:248] attempting to acquire leader lease group-sync-operator/085c249a.redhat.io...
1.671728101939729e+09 INFO Starting server {"kind": "health probe", "addr": "[::]:8081"}
I1222 16:56:11.850650 1 leaderelection.go:258] successfully acquired lease group-sync-operator/085c249a.redhat.io
1.6717281718509688e+09 INFO Starting EventSource {"controller": "groupsync", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GroupSync", "source": "kind source: *v1alpha1.GroupSync"}
1.6717281718510113e+09 INFO Starting Controller {"controller": "groupsync", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GroupSync"}
1.6717281718507807e+09 DEBUG events Normal {"object": {"kind":"Lease","namespace":"group-sync-operator","name":"085c249a.redhat.io","uid":"35b84246-9a55-43b1-afb2-82acad22f6b0","apiVersion":"coordination.k8s.io/v1","resourceVersion":"6777972"}, "reason": "LeaderElection", "message": "group-sync-operator-controller-manager-764dbc8b48-m9jdb_f295766d-cdd7-4479-85f5-f38d4a7cda25 became leader"}
1.6717281719518456e+09 INFO Starting workers {"controller": "groupsync", "controllerGroup": "redhatcop.redhat.io", "controllerKind": "GroupSync", "worker count": 1}
1.6717281720531447e+09 INFO controllers.GroupSync Beginning Sync {"groupsync": "group-sync-operator/groupsync", "Provider": "azure"}
1.6717281792370646e+09 ERROR syncer_azure Failed to get Group members for Group {"Group":
github.com/redhat-cop/group-sync-operator/pkg/syncer.(*AzureSyncer).Sync
/home/runner/work/group-sync-operator/group-sync-operator/pkg/syncer/azure.go:278
github.com/redhat-cop/group-sync-operator/controllers.(*GroupSyncReconciler).Reconcile
/home/runner/work/group-sync-operator/group-sync-operator/controllers/groupsync_controller.go:112
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.12.2/pkg/internal/controller/controller.go:234
1.6717281792372632e+09 ERROR controllers.GroupSync Failed to Complete Sync {"groupsync": "group-sync-operator/groupsync", "Provider": "azure", "error": "error status code received from the API"}
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 at pkg/syncer/azure.go:278, where the logged failure occurs, and follow the AzureSyncer.Sync call from controllers/groupsync_controller.go:112. Use the provided Azure group-sync failure and API status error as the starting point for investigation. Done means Azure groups sync successfully after upgrading to Operator v0.0.23 without the reported API error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go, kubernetes
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100