Improve tracing / reconciliation when clusterOperation.reconciliationPaused is set to true
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the reconciliation path that handles clusterOperation.reconciliationPaused and review how errors are logged and emitted as CR events. Done means a paused cluster does not produce repeated dependency errors and instead clearly logs that reconciliation is paused; check whether the behavior applies to other operators as suggested.
Written by the indexing model from the issue text.
Description
When clusterOperation.reconciliationPaused is set to true, the operator still runs through reconciliation without applying anything. This leads to errors in the operator logs when required dependencies are not applied and missing (e.g. retrieve a nodeport from a service etc.)
2024-02-13T09:18:40.770253Z ERROR stackable_operator::logging::controller: Failed to reconcile objec │
│ t controller.name="opacluster.opa.stackable.tech" error=reconciler for object OpaCluster.v1alpha1.op │
│ a.stackable.tech/opa.platform failed error.sources=[failed to apply role Service, Kubernetes reporte │
│ d error: ApiError: services "opa" not found: NotFound (ErrorResponse { status: "Failure", message: " │
│ services \"opa\" not found", reason: "NotFound", code: 404 }), ApiError: services "opa" not found: N │
│ otFound (ErrorResponse { status: "Failure", message: "services \"opa\" not found", reason: "NotFound │
│ ", code: 404 }), services "opa" not found: NotFound]
This shadows the real problem (in this case it was hard to see that the operator is actually not reconciling that cluster) and the errors is logged constantly in the operator and the CR events.
We need to improve the operator logging in this case to "ignore" errors and simply log that this cluster is currently not reconciled.
This may affect other operators as well.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 5
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 11
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.
More from stackabletech/opa-operator
-
type/bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
stackabletech/opa-operator#823 ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
stackabletech/opa-operator#766 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stackabletech/opa-operator#733 ·
-
Difficulty 2/5 Half a day Newbie friendliness 50/100
stackabletech/opa-operator#724 ·
-
type/bug
Difficulty 5/5 Over a week Newbie friendliness 20/100
stackabletech/opa-operator#718 ·
All issues in stackabletech/opa-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100