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.

Sign up for GitHub

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

Jump to bottom

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

Open
macmacs opened this issue Sep 15, 2017 · 5 comments · May be fixed by #28
Open

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

macmacs opened this issue Sep 15, 2017 · 5 comments · May be fixed by #28

Comments

@macmacs
Copy link

macmacs commented Sep 15, 2017

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?
@ibotty
Copy link
Owner

ibotty commented Sep 15, 2017

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
Copy link
Owner

ibotty commented Sep 15, 2017

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.

@macmacs
Copy link
Author

macmacs commented Sep 16, 2017

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 macmacs linked a pull request Sep 16, 2017 that will close this issue
Open
@malagant malagant mentioned this issue Oct 20, 2017
Open
@ibotty
Copy link
Owner

ibotty commented Oct 23, 2017

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

@mcanevet
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clusterrole updated
3 participants
@ibotty @mcanevet @macmacs