Replies: 7 comments 1 reply
-
Hey, we're seeing similar issues with 1.8.2. Do you know if this got better with 1.9.1? |
Beta Was this translation helpful? Give feedback.
-
Upgraded to 1.10.1 still getting that error |
Beta Was this translation helpful? Give feedback.
-
Any updates on this issue? |
Beta Was this translation helpful? Give feedback.
-
Has anyone figured out what to make of these errors? Looking for a safe way to know when to ignore these, perhaps instead look for warnings on cert renewal instead. |
Beta Was this translation helpful? Give feedback.
-
I have the exact same error for every certificate in my cluster. My deduction is that this message appear only when the cert-manager pod is starting which lead to an error of the issuer because it may not me ready to process certificates. Otherwise, everything is working as expected... I would be happy to have an answer from the dev team about this ! |
Beta Was this translation helpful? Give feedback.
-
Adding our $0.02 to this as well. We see these in our Openshift 4.12 cluster with version 1.13.1 of cert-manager.
|
Beta Was this translation helpful? Give feedback.
-
I think the error is temporary and can be ignored. I think that it occurs when cert-manager controller Pod starts up and reconciles Order and / or Challenge resources before it has reconciled the associated Issuer / ClusterIssuer resources. More investigation is needed, but here's what I've seen so far: The error is defined here: cert-manager/pkg/acme/accounts/registry.go Lines 32 to 33 in d2f6bbe And raised by this function: cert-manager/pkg/acme/accounts/registry.go Lines 157 to 168 in d2f6bbe When Order or Challenge resources are reconciled and when an in-memory cached ACME client is not found: cert-manager/pkg/controller/acmeorders/sync.go Lines 84 to 87 in d2f6bbe cert-manager/pkg/controller/acmechallenges/sync.go Lines 126 to 129 in d2f6bbe The cached ACME client gets created when cert-manager reconciles ACME Issuer or ClusterIssuer resources cert-manager/pkg/issuer/acme/setup.go Lines 218 to 221 in d2f6bbe |
Beta Was this translation helpful? Give feedback.
-
Hi everybody,
we observed a confusing error messages in our logs after restarting our cert-manager deployments on our clusters. Every time, the cert-manager and the cainjector is restarted, we log the following error:
The orders have the state
valid
and all the certificates are fetched correctly. The challenges succeeded. Since actually nothing went wrong, we tend to ignore these errors until we really have trouble with requesting and fetching certificates.We got these errors through the versions 0.6.1 to 1.8.2
ingress-nginx is v0.51.0
external-dns is v0.11.0
Kubernetes is v1.19.15
Is this behaviour known and can you confirm, that it is some kind of logging noise?
If yes, do they still occur in higher versions?
And if not, why does it occur although nothing went wrong at all?
Thank you in advance and best regards
Beta Was this translation helpful? Give feedback.
All reactions