[
https://issues.jboss.org/browse/JBIDE-26333?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-26333 at 9/4/18 4:43 AM:
------------------------------------------------------------------
I am completely unable to launch cdk 3.6.0.Alpha2 on the command line (no Eclipse tooling
involved). To me the cdk build looks broken. The error that we see in Eclipse is correct,
because the CDK could *NOT* be reached.
Here's what I did:
# start cdk without any flags.
Result: registration fails, user is told that the system already is registered. Verifying
this in
access.redhat.com shows that no system is registered. So the claim seems bogus.
{code}
Error to register VM: ssh command error:
command : sudo -E subscription-manager register --auto-attach --username
adietish(a)redhat.com --password ********
err : exit status 64
output : This system is already registered. Use --force to override
{code}
# start cdk with the --skip-registration flag.
Result: one is told that the cdk is started but that the server is running with an unknown
authority. Furthermore the minishift profile could not be set because logging in failed.
{code}
The server is accessible via web console at:
https://192.168.64.51:8443
error: The server uses a certificate signed by unknown authority. You may need to use the
--certificate-authority flag to provide the path to a certificate file for the certificate
authority, or --insecure-skip-tls-verify to bypass the certificate check and use insecure
connections.
Could not set oc CLI context for 'minishift' profile: Error during setting
'minishift' as active profile: Unable to login to cluster
{code}
# start cdk using --skip-registration and --insecure-skip-tls-verify
Result: cdk complains that --insecure-skip-tls-verify is an unknown flag.
{code}
Error: unknown flag: --insecure-skip-tls-verify
{code}
was (Author: adietish):
So I am completely unable to launch cdk 3.6.0.Alpha2 on the command line (no Eclipse
tooling involved). To me the cdk build looks broken. The error that we see in Eclipse is
correct, because the CDK could *NOT* be reached.
Here's what I did:
# start cdk without any flags.
Result: registration fails, user is told that the system already is registered. Verifying
this in
access.redhat.com shows that no system is registered. So the claim seems bogus.
{code}
Error to register VM: ssh command error:
command : sudo -E subscription-manager register --auto-attach --username
adietish(a)redhat.com --password ********
err : exit status 64
output : This system is already registered. Use --force to override
{code}
# start cdk with the --skip-registration flag.
Result: one is told that the cdk is started but that the server is running with an unknown
authority. Furthermore the minishift profile could not be set because logging in failed.
{code}
The server is accessible via web console at:
https://192.168.64.51:8443
error: The server uses a certificate signed by unknown authority. You may need to use the
--certificate-authority flag to provide the path to a certificate file for the certificate
authority, or --insecure-skip-tls-verify to bypass the certificate check and use insecure
connections.
Could not set oc CLI context for 'minishift' profile: Error during setting
'minishift' as active profile: Unable to login to cluster
{code}
# start cdk using --skip-registration and --insecure-skip-tls-verify
Result: cdk complains that --insecure-skip-tls-verify is an unknown flag.
{code}
Error: unknown flag: --insecure-skip-tls-verify
{code}
CDK server adapter: errror while creating Openshift connection after
start of CDK 3.6 server adapter
----------------------------------------------------------------------------------------------------
Key: JBIDE-26333
URL:
https://issues.jboss.org/browse/JBIDE-26333
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, openshift
Affects Versions: 4.9.0.AM3
Reporter: Ondrej Dockal
Assignee: Andre Dietisheim
Labels: cdk_server_adapter
Fix For: 4.9.0.Final
Attachments: CDKStartupOSconnError.gif
I am watching error being thrown just after cdk server adapter is created and OS
untrusted ssl cert. accepted. Also, this throws an Error dialog (making itests to fail).
{code}
null
org.jboss.tools.openshift.cdk.server
Error
Sun Sep 02 20:16:37 CEST 2018
Error contacting OpenShift
org.jboss.tools.openshift.internal.cdk.server.core.adapter.OpenShiftNotReadyPollingException:
The CDK VM is up and running, but OpenShift is unreachable at url
https://192.168.42.235:8443. The VM may not have been registered successfully. Please
check your console output for more information
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:145)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.checkOpenShiftHealth(MinishiftPoller.java:124)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.MinishiftPoller.onePing(MinishiftPoller.java:79)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.onePingSafe(AbstractCDKPoller.java:90)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.AbstractCDKPoller.getCurrentStateSynchronous(AbstractCDKPoller.java:78)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController.handleProcessTerminated(AbstractCDKLaunchController.java:232)
at
org.jboss.tools.openshift.internal.cdk.server.core.adapter.controllers.AbstractCDKLaunchController$4.run(AbstractCDKLaunchController.java:188)
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)