-
Notifications
You must be signed in to change notification settings - Fork 116
caCertificate not removed/updated (ExtendedValidationFailed) #68
Comments
Removing the old Could you try to remove it manually and can confirm that fixes the issue? (I can follow up with a PR if that's confirmed.) |
Yes, I can confirm that manually removing |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/reopen |
@tnozicka: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Ran into this issue with OpenShift 4.3 - also resolved by manually removing caCertificate. |
I enabled
kubernetes.io/tls-acme
on a route that so far used a non-ACME certificate. Doing so, however, resulted ExtendedValidationFailed error.As far as I can tell this is caused by the fact that, for the old cert,
spec.tls.caCertificate
was set to the certificate authority. When openshift-acme issues a certificate it includes the CA cert inspec.tls.certificate
however. This causes, rightfully, a validation error since there are now two CA certs in the chain. I believe openshift-acme should either a) removespec.tls.caCertificate
if it exists or b) move the CA cert fromspec.tls.certificate
tospec.tls.caCertificate
.Route before enabling ACME:
Route after enabling ACME:
The text was updated successfully, but these errors were encountered: