Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cert-manager/certificates-issuing: re-queuing item due to optimistic locking on resource" #6862

Open
Kaali09 opened this issue Mar 18, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@Kaali09
Copy link

Kaali09 commented Mar 18, 2024

Describe the bug:
We are seeing the error message below in the cert-manager pod logs whenever we attempt to create or renew a certificate. However, certificate creation and renewal are functioning properly. Nevertheless, this error message is causing us to suspect that there may be an issue in the system.

I0318 06:34:56.581056       1 controller.go:162] "cert-manager/certificates-readiness: re-queuing item due to optimistic locking on resource" key="kafka-hasty-electron/kafka-cert-tls" error="Operation cannot be fulfilled on certificates.cert-manager.io \"kafka-cert-tls\": the object has been modified; please apply your changes to the latest version and try again"
I0318 06:34:56.582609       1 conditions.go:192] Found status change for Certificate "kafka-cert-tls" condition "Ready": "False" -> "True"; setting lastTransitionTime to 2024-03-18 06:34:56.582600641 +0000 UTC m=+2055.224754078
I0318 06:34:56.610545       1 controller.go:162] "cert-manager/certificates-issuing: re-queuing item due to optimistic locking on resource" key="kafka-hasty-electron/kafka-cert-tls" error="Operation cannot be fulfilled on certificates.cert-manager.io \"kafka-cert-tls\": the object has been modified; please apply your changes to the latest version and try again"
I0318 06:34:56.636132       1 controller.go:162] "cert-manager/certificates-key-manager: re-queuing item due to optimistic locking on resource" key="kafka-hasty-electron/kafka-cert-tls" error="Operation cannot be fulfilled on certificates.cert-manager.io \"kafka-cert-tls\": the object has been modified; please apply your changes to the latest version and try again"

Expected behaviour:
Cert-manager shouldn't be generating these error messages when certificate creation and renewal are functioning properly

Steps to reproduce the bug:

  1. Install version v1.12.9 of cert-manager.
  2. Attempt to create a certificate.
  3. Check the logs of the cert-manager pod for any error messages.

Anything else we need to know?:

Environment details::

  • Kubernetes version: v1.24.17
  • Cloud-provider/provisioner: AWS
  • cert-manager version: v1.12.9
  • Install method: helm

/kind bug

@jetstack-bot jetstack-bot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 18, 2024
@Kaali09 Kaali09 changed the title Seeing weird message in the cert-manager logs [ "error":"certificate still in a pending state, the request will be retried: Not yet available" ] Encountering strange messages in the cert-manager logs. [ "error":"certificate still in a pending state, the request will be retried: Not yet available" ] Mar 18, 2024
@Kaali09 Kaali09 changed the title Encountering strange messages in the cert-manager logs. [ "error":"certificate still in a pending state, the request will be retried: Not yet available" ] cert-manager/certificates-issuing: re-queuing item due to optimistic locking on resource" Mar 18, 2024
@inteon
Copy link
Member

inteon commented Mar 18, 2024

You can enable ServerSideApply on all components to prevent these errors from happening.
However, these errors should not lead to any issues, they will self-resolve when retried.

You can learn more about setting feature flags like ServerSideApply on https://cert-manager.io/docs/installation/configuring-components/.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants