[jbosstools-issues] [JBoss JIRA] (JBIDE-26869) CRC server adapter: OpenShift connection that is created is unusable at times

[André Dietisheim (Jira)]

    [ https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800377#comment-13800377 ] 

André Dietisheim edited comment on JBIDE-26869 at 10/16/19 8:47 AM:
--------------------------------------------------------------------

interestingly, in such situations 
* **oc**: login doesnt work either:
{code}
$ ~/.crc/bin/oc login https://api.crc.testing:6443
Error from server (InternalError): Internal error occurred: unexpected response: 400
{code}
* **web console**: login doesnt work when using developer/developer. Login with kubeadmin works though but shows in the dashboard that the cluster is in an error state. 

After some waiting both oc and the web console allows login via developer/developer. The error is also gone.
For the Eclipse connection, refresh doesnt help. But editing the connection (faking a change and getting back to original) helps though and login is possible.

[~kumarpraveen] any idea why waiting is required?


was (Author: adietish):
interestingly, in such situations 
* login via oc doesnt work either:
{code}
$ ~/.crc/bin/oc login https://api.crc.testing:6443
Error from server (InternalError): Internal error occurred: unexpected response: 400
{code}
* login in web console doesnt work when using developer/developer. Login with kubeadmin works though but shows in the dashboard that the cluster is in an error state. 

After some waiting both oc and the web console allows login via developer/developer. The error is also gone.
For the Eclipse connection, refresh doesnt help. But editing the connection (faking a change and getting back to original) helps though and login is possible.

[~kumarpraveen] any idea why waiting is required?

> CRC server adapter: OpenShift connection that is created is unusable at times
> -----------------------------------------------------------------------------
>
>                 Key: JBIDE-26869
>                 URL: https://issues.jboss.org/browse/JBIDE-26869
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.13.0.AM1
>         Environment: CRC Beta5
>            Reporter: André Dietisheim
>            Assignee: André Dietisheim
>            Priority: Critical
>             Fix For: 4.13.0.Final
>
>         Attachments: crc-connection-error.mp4, start-crc-error-openshift-conn.mp4
>
>
> *Steps* - not reproducibe at 100%, happens from time to time:
> # ASSERT: have ~/.crc folder killed
> # EXEC: create new CRC server adapter & Start it
> # ASSERT: OpenShift connection is created
> *Result:*
> Connection fails to authorize, reports that it cannot access resources using system:anonymous. Refreshing the connection doesn't help, so it's apparently not a timing issue (ex. creating the connection before the cluster is fully up and running)
> {code}
> com.openshift.restclient.authorization.ResourceForbiddenException: forbidden: User "system:anonymous" cannot get path "/oauth/authorize" forbidden: User "system:anonymous" cannot get path "/oauth/authorize"
> 	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:111)
> 	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:66)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> 	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> 	at okhttp3.RealCall.execute(RealCall.kt:66)
> 	at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.tryAuth(OpenShiftAuthenticator.java:109)
> 	at com.openshift.internal.restclient.okhttp.OpenShiftAuthenticator.authenticate(OpenShiftAuthenticator.java:62)
> 	at okhttp3.internal.http.RetryAndFollowUpInterceptor.followUpRequest(RetryAndFollowUpInterceptor.kt:213)
> 	at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:102)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> 	at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:55)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:112)
> 	at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:87)
> 	at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.kt:184)
> 	at okhttp3.RealCall.execute(RealCall.kt:66)
> 	at com.openshift.internal.restclient.DefaultClient.request(DefaultClient.java:315)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:307)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:275)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:243)
> 	at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:226)
> 	at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:423)
> 	at com.openshift.internal.restclient.authorization.AuthorizationContext.isAuthorized(AuthorizationContext.java:63)
> 	at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:237)
> 	at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> 	at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureOpenshift(ConfigureCRCFrameworksListener.java:102)
> 	at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener.configureFrameworks(ConfigureCRCFrameworksListener.java:73)
> 	at org.jboss.tools.openshift.internal.crc.server.core.listeners.ConfigureCRCFrameworksListener$1.run(ConfigureCRCFrameworksListener.java:66)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)