[jbosstools-issues] [JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this

[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ] André Dietisheim edited comment on JBIDE-27019 at 2/10/20 6:14 AM: ------------------------------------------------------------------- [~odockal] that's odd, I cannot reproduce this. I get the console opened at the correct url, namely {code}https://console-openshift-console.apps-crc.testing/{code} The thing that makes me wondering is the following error message that you report: {code} com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) {code} The client library complains that it cannot retrieve config maps from the cluster. That's where the client library would fetch the url for the console from. Apparently this retrieval failed and Eclipse thus fallen back to the default host url which is indeed {code}https://api.crc.testing:6443/{code} This url is indeed also reporting *Forbidden* for me, it seems not valid any longer. Retrieving of config maps on the other hand should always succeed, config maps are a completely valid kind of resources, failing to request this kind of resources shouldn't ever fail in a functional OpenShift cluster, that's very very unexpected. It would be "valid" that we cannot find the config map that stores the url for the console, but the client lib here fails in the prior step, it cannot retrieve *ANY* config map. I thus suspect that your crc wasn't fully started or is corrupt. You seem to confirm this by your step 6: {code} 6. ASSERT: One can connect to OS via web console {code} [~odockal] Can you still reproduce this bug? [~jeffmaury] Can you reproduce this? was (Author: adietish): [~odockal] that's odd, I cannot reproduce this. I get the console opened at the correct url, namely {code}https://console-openshift-console.apps-crc.testing/{code} The thing that makes me wondering is the following error message that you report: {code} com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap' at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149) at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135) {code} The client library complains that it cannot retrieve config maps from the cluster. That's where the client library would fetch the url for the console from. Apparently this retrieval failed and Eclipse thus falled back to the default host url which is indeed {code}https://api.crc.testing:6443/{code} This retrieval should always succeed, config maps are a completely valid kind of resources, this shouldn't ever happen in an OpenShift cluster, that's very very unexpected. It would be "valid" that we cannot find the config map that stores the url for the console, but the client lib here fails in the prior step, it cannot even retrieve *ANY* config map. I thus suspect that your crc wasn't fully started or is corrupt. You seem to confirm this by your step 6: {code} 6. ASSERT: One can connect to OS via web console {code} [~odockal] Can you still reproduce this bug? [~jeffmaury] Can you reproduce this? -- This message was sent by Atlassian Jira (v7.13.8#713008)