[jbosstools-issues] [JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.

Martin Malina (JIRA) issues at jboss.org
Thu Jul 7 05:43:00 EDT 2016


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

Martin Malina commented on JBIDE-22609:
---------------------------------------

For one thing, vagrant up returns 1 when the credentials provided are wrong.
And there's this at the end of the output:
{code}
==> default: Registering box with vagrant-registration...
Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html
Registering to: subscription.rhn.redhat.com:443/subscription
{code}
But afaik you don't parse this output, so that's not useful.

You could at least use the return code? But true, it wouldn't improve things much - you already notice that openshift is not running.

One thing is for sure - we should handle this use case better. Especially creating a connection with this strange ip (10.0.2.15) shouldn't happen. But this is more of a problem with service manager. I created this upstream issue:
https://github.com/projectatomic/vagrant-service-manager/issues/299

> Provided wrong credentials, CDK server adapter says "started" even though it is not.
> ------------------------------------------------------------------------------------
>
>                 Key: JBIDE-22609
>                 URL: https://issues.jboss.org/browse/JBIDE-22609
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.0.Final
>         Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10
>            Reporter: Radim Hopp
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 4.4.x
>
>
> When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x)



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list