Closed albertpuente closed 3 years ago
This is probably related to https://github.com/opendevstack/ods-provisioning-app/pull/630.
Tried disabling the preflight checks as follows:
services.openshift.enabled=false
but the error is the same:
cc @stitakis
I understand by the following errors that the OpenShift REST client being used won't support the API provided by OCP4.
2021-06-15 14:19:03 INFO c.o.i.restclient.ApiTypeMapper - Can't access legacy endpoint oapi
java.lang.IllegalArgumentException: Invalid character: <
at org.jboss.dmr.JSONParserImpl.invalid(JSONParserImpl.java:136)
2021-06-15 14:19:03 INFO c.o.i.restclient.ApiTypeMapper - Can't access legacy endpoint api
com.openshift.restclient.NotFoundException: Not Found
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:125)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:69)
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
at okhttp3.internal.connection.RealCall.execute(RealCall.kt:154)
at com.openshift.internal.restclient.ApiTypeMapper.request(ApiTypeMapper.java:273)
at com.openshift.internal.restclient.ApiTypeMapper.readEndpoint(ApiTypeMapper.java:261)
What OCP 4 version have you used to test it? We're targeting OCP 4.7.13 at the moment.
Those invalid character < errors are familiar to me... can it be that the request returns a HTML page?
maybe a wrong url? can you go and curl the url you are using - and see what is returned, the thing expects json it seems - and it's some x/hmtl
Looks like oauth is kicking in - and that is why you get an html page - just enter it in a browser? - is there something wrongly configured, or tokens NOT sent around?
@stitakis can you work with the team to get this resolved?
@clemensutschig @metmajer I got access to the ocp4 cluster. I'll take a look together with Albert and Felipe
@albertpuente @felipecruz91 regarding this exception:
2021-06-15 13:40:26 INFO c.o.i.restclient.ApiTypeMapper - Can't access legacy endpoint api
com.openshift.restclient.NotFoundException: Not Found
Did you have the chance to verify if...
@clemensutschig @metmajer an update on this...
we found out so far that:
A. the first attempt to disable the service with the config flag services.openshift.enabled=false
failed because the same property was defined as services.openshift.enabled=true
below in the configuration application.properties
. We tested this flag services.openshift.enabled=false
and worked expected.
B. the property openshift.api.uri
contains the wrong url. We will find the right url for oc4 and test again.
@clemensutschig @metmajer @michaelsauter
it was a configuration issue. No bug at all.
We found the right value for the property openshift.api.uri
and successfully tested the prov-app.
I'll close this item.
Thanks @felipecruz91 and @albertpuente for the support!
Describe the bug Following an apparently successful installation of ODS4 in an OCP4 cluster, the provisioning app displays an error whenever a new project is created.
To Reproduce Steps to reproduce the behavior:
Expected behavior A new ODS project is created with all its components.
Screenshots![image](https://user-images.githubusercontent.com/4146512/122063511-a04a4880-cdf0-11eb-8fc3-8f1cfcbd0812.png)
Affected version (please complete the following information):
Log Output (ensure to remove any confidential information like tokens, project names, etc.
@felipecruz91 @stitakis