Description of problem: When a re-encrypt route's destinationCAcertificate expires, the route returns 503s with no further explanation
Version-Release number of selected component (if applicable): 126.96.36.199-1.git.0.86dc49a
How reproducible: always
Steps to Reproduce:
1. Create a re-encrypt route with an expired destinationCAcertificate
route returns 503 with no indication that the certificate is expired
the user should be notified that their certificate is expired
Is there anything in the router pod log?
Ram, do the extended validation changes we are backporting fix this?
Depends on where the error is coming from. @Sten, what does
$ oc get route <route-name> -o yaml
Does it say something like extended validation failed for the certificate.
If that's the case, @Ben then this is fixed with the backports for the extended validation changes to 3.2 and 3.3
Otherwise, its something else we need to look at. Thx
Closing due to inactivity. If it is still happening, please re-open and provide the requested information.
We haven't seen this issue since ~3.3