[
https://issues.jboss.org/browse/JBIDE-26869?page=com.atlassian.jira.plugi...
]
André Dietisheim edited comment on JBIDE-26869 at 9/27/19 4:31 AM:
-------------------------------------------------------------------
[~kumarpraveen] thx for chiming in. I also believe that crc came up faulty when this
happens. Here's the output:
{code}
$ crc status --log-level debug
CRC VM: Running
OpenShift: Running (v4.x)
Disk Usage: 11.16GB of 16.09GB (Inside the CRC VM)
Cache Usage: 10.75GB
Cache Directory: /Users/adietish/.crc/cache
{code}
btw. logging in using oc also fails:
{code}
$ oc login 192.168.64.104
The server is using a certificate that does not match its hostname: x509: cannot validate
certificate for 192.168.64.104 because it doesn't contain any IP SANs
You can bypass the certificate check, but any data you send to the server could be
intercepted by others.
Use insecure connections? (y/n): y
error: couldn't get
https://192.168.64.104:443/.well-known/oauth-authorization-server:
unexpected response status 503
{code}
This looks like an issue in CRC, nothing the tooling is faulty of.
was (Author: adietish):
[~kumarpraveen] thx for chiming in. I also believe that crc came up faulty when this
happens. Here's the output:
{code}
$ crc status --log-level debug
CRC VM: Running
OpenShift: Running (v4.x)
Disk Usage: 11.16GB of 16.09GB (Inside the CRC VM)
Cache Usage: 10.75GB
Cache Directory: /Users/adietish/.crc/cache
{code}
btw. logging in using oc also fails:
{code}
$ oc login 192.168.64.104
The server is using a certificate that does not match its hostname: x509: cannot validate
certificate for 192.168.64.104 because it doesn't contain any IP SANs
You can bypass the certificate check, but any data you send to the server could be
intercepted by others.
Use insecure connections? (y/n): y
error: couldn't get
https://192.168.64.104:443/.well-known/oauth-authorization-server:
unexpected response status 503
{code}
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
Reporter: André Dietisheim
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.13.0.Final
Attachments: crc-connection-error.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)