[jbosstools-issues] [JBoss JIRA] (JBDS-3795) Cant start CDK

[Hardy Ferentschik (JIRA)]

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

Hardy Ferentschik commented on JBDS-3795:
-----------------------------------------

{quote}
I was just running vagrant up, no other commands. I don't get that pull error today. Maybe it was some issue with the infrastructure that has been resolved since?
{quote}
Not sure. There is for sure an issue with image caching atm. See above.

{quote}
With service-manager 1.0.1 I was able to start cdk flawlessly in cli - I even got the openshift info.
{quote}
good

{quote}
But when I tried again with service-manager 1.0.0 (after vagrant destroy), I still have the problem of not seeing the openshift info.
{quote}
1.0.0? Did you mean 1.0.1? And where do you not see the OpenShift info? You mean during _vagrant up_? Using service-manager 1.0.0 does indeed not display this.

> Cant start CDK
> --------------
>
>                 Key: JBDS-3795
>                 URL: https://issues.jboss.org/browse/JBDS-3795
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: cdk, installer
>    Affects Versions: 9.1.0.CR1
>            Reporter: Alexey Kazakov
>            Assignee: Hardy Ferentschik
>            Priority: Blocker
>              Labels: havoc, respin-c
>             Fix For: 9.1.0.CR1
>
>         Attachments: screenshot-1.png
>
>
> CDK server adapter is not started when using JBDS + CDK April 8th build even after updating vagrant-service-manager to 1.0.1.
> "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments."
> I can access the OS console: https://10.1.2.2:8443/console
> The console output looks OK too:
> {code}
> Bringing machine 'default' up with 'virtualbox' provider...
> ==> default: Importing base box 'cdkv2'...
> Progress: 10%
> Progress: 20%
> Progress: 90%
> ==> default: Matching MAC address for NAT networking...
> ==> default: Setting the name of the VM: rhel-ose_default_1460496916213_82608
> ==> 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: 
>     default: Vagrant insecure key detected. Vagrant will automatically replace
>     default: this with a newly generated keypair for better security.
>     default: 
>     default: Inserting generated public key within guest...
>     default: Removing insecure key from the guest if it's present...
>     default: Key inserted! Disconnecting and reconnecting using new SSH key...
> ==> 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: Copying TLS certificates to C:/DeveloperPlatform/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker
> ==> default: Rsyncing folder: /cygdrive/c/DeveloperPlatform/cdk/components/rhel/rhel-ose/ => /vagrant
> ==> default: Running provisioner: shell...
>     default: Running: inline script
> ==> default: Running provisioner: shell...
>     default: Running: inline script
> ==> default: 
> ==> default: Successfully started and provisioned VM with 2 cores and 3072 MB of memory.
> ==> default: To modify the number of cores and/or available memory set the environment variables
> ==> default: VM_CPU respectively VM_MEMORY.
> ==> default: 
> ==> default: You can now access the OpenShift console on: https://10.1.2.2:8443/console
> ==> default: 
> ==> default: To use OpenShift CLI, run:
> ==> default: $ vagrant ssh
> ==> default: $ oc login 10.1.2.2:8443
> ==> default: 
> ==> default: Configured users are (<username>/<password>):
> ==> default: openshift-dev/devel
> ==> default: admin/admin
> ==> default: 
> ==> default: If you have the oc client library on your host, you can also login from your host.
> {code}



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