openshift-letsencrypt icon indicating copy to clipboard operation
openshift-letsencrypt copied to clipboard

patch_route() doesn't work - Route won't be updated.

Open macmacs opened this issue 6 years ago • 5 comments

When I looked at the watcherpod's log, I noticed, that all steps work fine. Even the generation of the data object to patch the route with is correct. I took this data object and passed it to openshift via oc patch route <route-name> -p <data>. This worked and the route was changed to https.

By turning on debugging in common.sh via set -x and removing 2> /dev/null in line 62 i got the message curl: (22) NSS: client certificate not found (nickname not specified).

After this, cleanup proceeds and the route didn't change.

Any ideas, why this is failing?

macmacs avatar Sep 15 '17 17:09 macmacs

I don't remember having had that problem.

Did you try the oc patch with the same credentials? (You can find them in /run/secrets/...)

ibotty avatar Sep 15 '17 21:09 ibotty

BTW: I plan to migrate to openshift-acme, because having two services that do the same thing is not in my interest. If you have not yet started using openshift-letsencrypt, you might prefer using the other project. That is, if you did not have reasons to prefer that project. If so, please do tell me, so I might reconsider.

ibotty avatar Sep 15 '17 21:09 ibotty

I tried oc patch ... with the service account's token and got The Route "<route>" is invalid: spec.tls: Invalid value: route.TLSConfig{...}: field is immutable

I think it's because of 15772.

The reason for this way of using openshift-letsencrypt was that I didn't get openshift-acme to work either....

macmacs avatar Sep 16 '17 10:09 macmacs

Is that on openshift-online or a diy installed openshift cluster? Am I correct, that it's openshift 3.6?

ibotty avatar Oct 23 '17 10:10 ibotty

@ibotty do you mean this project is dead? If so, maybe you should put a notice in the README.md.

mcanevet avatar Feb 27 '18 09:02 mcanevet