eventing
eventing copied to clipboard
pingsource-controller Operation cannot be fulfilled on deployments.apps "pingsource-mt-adapter"
Describe the bug We keep getting error message from our pingsources
Warning InternalError 42s (x8 over 26m) pingsource-controller Operation cannot be fulfilled on deployments.apps "pingsource-mt-adapter": the object has been modified; please apply your changes to the latest version and try again
commit: 4d6e1fc
duration: 0.05510259
error: Operation cannot be fulfilled on deployments.apps "pingsource-mt-adapter": the object has been modified; please apply your changes to the latest version and try again
knative.dev/controller: knative.dev.eventing.pkg.reconciler.pingsource.Reconciler
knative.dev/key: zs-k8sprofiler/profile-cron-handler.b94424d3-f654-41fb-bbe5-8f947c721319
knative.dev/kind: sources.knative.dev.PingSource
knative.dev/pod: eventing-controller-54dcd89dfd-fmmch
knative.dev/traceid: a392bd29-b5de-4928-8830-613ce138292c
level: error
logger: controller
msg: Reconcile error
stacktrace: knative.dev/pkg/controller.(*Impl).handleErr
knative.dev/[email protected]/controller/controller.go:566
knative.dev/pkg/controller.(*Impl).processNextWorkItem
knative.dev/[email protected]/controller/controller.go:543
knative.dev/pkg/controller.(*Impl).RunContext.func3
knative.dev/[email protected]/controller/controller.go:491
ts: 2023-12-06T17:49:05.471Z
}
This message comes in an order "Unable to reconcile the receive adapter" "Returned an error" "Reconcile error"
it's constantly reconciling with around 10% "Reconcile error" and following with success, and don't seems affect the pingsource-mt-adapter pod's status
Expected behavior The eventing-controller should not produce these "Reconcile error" consistently when there is no new change added in the cluster.
Knative release version 1.9.0
cc @pierDipi
Is this still an issue in recent versions 1.12 and/or 1.11 ?
We should try to understand what other controller is modifying the pingsource-mt-adapter deployment.
How did you install Eventing? Using YAML or the operator ?
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.