[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Roland Grunberg commented on JBIDE-23043:
-----------------------------------------
I'm able to reproduce and at least in my case, bcprov 1.51 gets installed along with bcpkix 1.52. PEMParser (from bcpkix 1.52) extends PemReader (from bcprov 1.51) and it's more than likely this isn't supported.
It's strange that p2 is actually choosing to go with bcprov 1.51 given that 1.52 is there (updates-docker-nightly contains bcprov/bcpkix 1.52). I haven't confirmed this yet, but the bouncycastle 1.52 bundles are all using ;resolution="optional" for all Import-Package statements (that's how they were contributed in 1.52) which is not how 1.51 does it and might be causing this problem.
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, target-platform
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
> Assignee: Jeff Johnston
> Priority: Blocker
> Fix For: 4.4.1.Final
>
> Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt
>
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4020) 'Download Remote URL' failed for Red Hat Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4020?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4020:
-----------------------------
Attachment: jbds3982_error-on-startup.png
jbds3982_installed-features.png
> 'Download Remote URL' failed for Red Hat Central
> ------------------------------------------------
>
> Key: JBDS-4020
> URL: https://issues.jboss.org/browse/JBDS-4020
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.1.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: jbds3982_error-on-startup.png, jbds3982_installed-features.png
>
>
> 0. Download this rpm [1].
> [1] http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.rpm...
> 1. install:
> {code}
> sudo su
> yum reinstall rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
> exit {code}
> 2. Check installation occurred:
> {code}
> ls /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/{code}
> 3. Run eclipse:
> {code}
> scl enable rh-eclipse46 bash
> cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
> ./eclipse{code}
> 4. Be patient! Initial startup with all the droplets and dropins could take a few minutes.
> 5. Error occurs on startup of Red Hat Central:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4020) 'Download Remote URL' failed for Red Hat Central
by Nick Boldt (JIRA)
Nick Boldt created JBDS-4020:
--------------------------------
Summary: 'Download Remote URL' failed for Red Hat Central
Key: JBDS-4020
URL: https://issues.jboss.org/browse/JBDS-4020
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Sub-task
Components: rpm, central-update
Affects Versions: 10.1.0.AM3
Reporter: Nick Boldt
Assignee: Nick Boldt
0. Download this rpm [1].
[1] http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.rpm...
1. install:
{code}
sudo su
yum reinstall rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
exit {code}
2. Check installation occurred:
{code}
ls /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/{code}
3. Run eclipse:
{code}
scl enable rh-eclipse46 bash
cd /opt/rh/rh-eclipse46/root/usr/lib64/eclipse/
./eclipse{code}
4. Be patient! Initial startup with all the droplets and dropins could take a few minutes.
5. Error occurs on startup of Red Hat Central:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23042:
----------------------------------------
Upstream issue - https://github.com/projectatomic/vagrant-service-manager/issues/383
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months