[jbosstools-issues] [JBoss JIRA] (JBIDE-23511) CDK start fails if you don't accept OpenShift certificate in time

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-23511:
---------------------------------------

{quote}
This is such a minor issue and since ti applies to all server adapters, and can't be fixed, I'm just going to reject it.
{quote}

Fair enough. But I don't agree that it happens to all server adapters. I mean the way things work, sure. But not the end result - typically a server does not need any interaction from the user to complete the startup. So you can start eap and go your own way and it will always succeed (and besides, it will start really fast, so usually you'll see it through anyway). But with CDK, it takes several minutes to start AND it requires user interaction (accepting the cert) for the startup to succeed. Granted, you only need to accept the cert once on a new vagrant box, but who starts cdk more than once before destroying it? :-P

> CDK start fails if you don't accept OpenShift certificate in time
> -----------------------------------------------------------------
>
>                 Key: JBIDE-23511
>                 URL: https://issues.jboss.org/browse/JBIDE-23511
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.2.Final
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.0.AM1
>
>
> This happened to me a couple of times and it's pretty annoying, but I'm not sure if anything can be done about it.
> When you launch cdk in devstudio and then forget about it and do something else, then when you get back to devstudio to actually play with cdk, you will see it fail horribly.
> This is because the startup time out has been reached and since you haven't accepted the openshift certificate, the prompt will be waiting for you and will cause time out.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)