[ https://issues.jboss.org/browse/JBIDE-21319?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21319: --------------------------------------- Here's the console output: {code} Bringing machine 'default' up with 'virtualbox' provider... ==> default: Clearing any previously set forwarded ports... ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat default: Adapter 2: hostonly ==> default: Forwarding ports... default: 22 => 2222 (adapter 1) ==> default: Running 'pre-boot' VM customizations... ==> default: Booting VM... ==> default: Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection timeout. Retrying... default: Warning: Remote connection disconnect. Retrying... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. ==> default: Configuring and enabling network interfaces... ==> default: Registering box with vagrant-registration... ==> default: Rsyncing folder: /Users/rasp/git/openshift-vagrant/cdk-v2/ => /vagrant ==> default: Running provisioner: shell... default: Running: /var/folders/w_/sj0mnvys69q9mw41clt1yww00000gn/T/vagrant-shell20151214-7677-11ro0pq.sh ==> default: [INFO] Skipping Docker configuration. Already done. ==> default: Running provisioner: shell... default: Running: /var/folders/w_/sj0mnvys69q9mw41clt1yww00000gn/T/vagrant-shell20151214-7677-gxstcg.sh ==> default: [INFO] Skipping pull of OpenShift image ==> default: [INFO] Preparing OpenShift config ==> default: [INFO] Waiting for OpenShift config files to be created ==> default: [INFO] Configuring OpenShift via /var/lib/origin/openshift.local.config/master/master-config.yaml ==> default: [INFO] Starting OpenShift server ==> default: [INFO] Waiting for OpenShift sever to come up ... ==> default: [INFO] ... ==> default: Running provisioner: shell... default: Running: inline script ==> default: ==> default: You can now access OpenShift console on: https://10.1.2.2:8443/console ==> default: ==> default: To use OpenShift CLI, run: ==> default: $ vagrant ssh ==> default: $ oc status ==> default: ==> default: To become a cluster-admin, add '--config' to oc commands: ==> default: $ vagrant ssh ==> default: $ oc status --config=/var/lib/origin/openshift.local.config/master/admin.kubeconfig {code} So you can see that it started up just fine. So some problem with detection of the startup being completed? -- This message was sent by Atlassian JIRA (v6.4.11#64026)