[jbosstools-issues] [JBoss JIRA] (JBDS-4592) Container Development Environment 3.2+ marked as started after minishift failure

[Rob Stryker (JIRA)]

     [ https://issues.jboss.org/browse/JBDS-4592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker resolved JBDS-4592.
-------------------------------
    Resolution: Rejected


Again, I believe the reason the server adapter is 'started' is because the command 'minishift status' returns that it is started. 

I cannot debug your registration failures, and can't know what's causing them. But, my experience has been that when registration errors occur, the underlying minishift command (and virtualbox / kvm / etc) all think the VM is up and running. So my server adapter keeps the state that matches minishift status. 

This is intentional. If I mark the server as stopped, but minishift status still thinks it's running, the next attempt to start the cdk will be a no-op, because the very first thing I'll do is check minishift status, which will tell me the cdk is up and running. 

ONLY IF you can show me that the server adapter is 'started' but 'minishift status' shows its stopped, will this be a bug.  Without proving that, this is intended behavior. 

Closing. Please re-open if you can prove that the server adapter and the command line are out-of-sync or returning different things. 

> Container Development Environment 3.2+ marked as started after minishift failure 
> ---------------------------------------------------------------------------------
>
>                 Key: JBDS-4592
>                 URL: https://issues.jboss.org/browse/JBDS-4592
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: cdk, runtime
>    Affects Versions: 11.1.0.GA
>         Environment: Red Hat JBoss Developer Studio
> Version: 11.1.0.GA
> Build id: GA-v20171023-1808-B1449
> OS: Windows 10, v.10.0, x86_64 / win32
>            Reporter: Denis Golovin
>            Assignee: Rob Stryker
>             Fix For: 11.2.0.AM2
>
>         Attachments: image.png
>
>
> Running Latest DevStudio nightly I am getting error during CDK 3.2.0-rc.1 start in server console
> {code}-- Starting local OpenShift cluster using 'virtualbox' hypervisor ...
> -- Minishift VM will be configured with ...
>    Memory:    4 GB
>    vCPUs :    2
>    Disk size: 20 GB
> -- Starting Minishift VM ....................................... OK
> -- Registering machine using subscription-manager
>    Registration in progress ................. FAIL [41s]
> Error to register VM: ssh command error:
> command : sudo -E subscription-manager register --auto-attach --username user at gmail.com --password 'password' 
> err     : exit status 70
> output  : Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
> Registering to: subscription.rhsm.redhat.com:443/subscription
> The system has been registered with ID: e3f3d67d-c835-4f7c-a2e9-ac9d94b9e2ef {code}
> CDK is still marked as started in servers view.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)