[jbosstools-issues] [JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)

Hardy Ferentschik (JIRA) issues at jboss.org
Thu Aug 24 04:49:00 EDT 2017


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

Hardy Ferentschik commented on JBIDE-24222:
-------------------------------------------

So closing Eclipse, manually editing the XML and then restarting got me past JBIDE-24881. 
Now I also can reproduce the issue. I start Minishift via the server adapter using xhyve as driver. Then I get all the startup output

{noformat}
-- Checking if xhyve driver is installed ... 
   Driver is available at /usr/local/bin/docker-machine-driver-xhyve
   Checking for setuid bit ... OK
-- Starting local OpenShift cluster using 'xhyve' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    8 GB
   vCPUs :    3
   Disk size: 20 GB
-- Starting Minishift VM ... |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   |   /   -   \   OK
-- Checking for IP address ... OK
-- Checking if external host is reachable from the Minishift VM ... 
   Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ... 
   Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 0% OK
-- Mounting hostfolders
   Mounting 'mac': '//192.168.99.1/MAC' as '/mnt/sda1/mac' ... OK
-- Importing cached images ...
   Importing openshift/origin-docker-registry:v3.6.0 [49.7s]
   Importing openshift/origin-haproxy-router:v3.6.0 [39.3s]
   Importing openshift/origin:v3.6.0 [36.5s]
-- OpenShift cluster will be configured with ...
   Version: v3.6.0
-- Checking `oc` support for startup flags ... 
   routing-suffix ... OK
   host-config-dir ... OK
   host-data-dir ... OK
   host-pv-dir ... OK
   host-volumes-dir ... OK
Starting OpenShift using openshift/origin:v3.6.0 ...
OpenShift server started.

The server is accessible via web console at:
    https://192.168.64.14:8443

You are logged in as:
    User:     developer
    Password: <any value>

To login as administrator:
    oc login -u system:admin

-- Waiting for persistent volumes to be created ... OK

-- Applying addon 'admin-user':..

-- Applying addon 'anyuid':.
 Add-on 'anyuid' changed the default security context constraints to allow pods to run as any user.
 Per default OpenShift runs containers using an arbitrarily assigned user ID.
 Refer to https://docs.openshift.org/latest/architecture/additional_concepts/authorization.html#security-context-constraints and
 https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-origin-specific-guidelines for more information.

-- Applying addon 'registry-route':........
Add-on 'registry-route' created docker-registry route. Please run following commands to login to the OpenShift docker registry:
$ eval $(minishift docker-env)
$ docker login -u developer -p `oc whoami -t` docker-registry-default.192.168.64.14.nip.io:443

-- Applying addon 'xpaas':........................................................................................
XPaaS OpenShift imagestream and templates installed
See https://github.com/openshift/openshift-ansible/tree/master/roles/openshift_examples/files/examples/v3.6
{noformat}

But after installing the add-ons the VM dies. The server adapter shows state "stopped" and if I verify this from a shell, the VM indeed died. 

I then tried to start Minishift from a new console using the xhyve driver. No issues there. I also could close the console/terminal, open a new one and Minishift is still running.

So it seems this is connected to how Eclipse starts the Minishift process. I don't really have the required insight there.

> CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-24222
>                 URL: https://issues.jboss.org/browse/JBIDE-24222
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.4.AM2
>         Environment: macos
> xhyve supervisor
> cdk3 beta3
>            Reporter: Andre Dietisheim
>            Assignee: Martin Malina
>            Priority: Critical
>              Labels: help_wanted
>             Fix For: 4.5.x
>
>         Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png, server-adapter-error.tiff
>
>




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



More information about the jbosstools-issues mailing list