[JBoss JIRA] (JBIDE-22193) Can't deploy locally built docker images
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22193?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22193:
-------------------------------------
I talked to Roland and it's actually more complicated than that. Docker tooling will need to provide a Registry Authentication extension, OpenShift tooling will need to provide an extension point so the password sent to docker login is the OpenShift connection token (token that changes everytime you connect to OpenShift, even with Basic Auth).
Relying on CLI login output is not really an option
> Can't deploy locally built docker images
> ----------------------------------------
>
> Key: JBIDE-22193
> URL: https://issues.jboss.org/browse/JBIDE-22193
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Reporter: Fred Bricon
> Priority: Blocker
>
> I can't deploy locally built docker images, pushed to the CDK docker registry, to OpenShift
> Trying to adapt the steps from https://github.com/redhat-developer-tooling/openshift-vagrant#how-to-run-... to Eclipse, I can't seem to be able to deploy anything
> Here's what the CLI generates from
> {quote}
> eval "$(vagrant service-manager env docker)"
> $ oc login 10.1.2.2:8443 -u openshift-dev -p devel
> Login successful.
> $ oc new-project my-ghost
> Now using project "my-ghost" on server "https://10.1.2.2:8443".
> $ docker pull ghost
> $ docker tag ghost hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ docker login -u openshift-dev -p `oc whoami -t` -e foo(a)bar.com hub.openshift.rhel-cdk.10.1.2.2.xip.io
> $ docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/my-ghost/ghost
> $ oc new-app --image-stream=ghost --name=ghost
> $ oc expose service ghost --hostname=my-ghost-blog.rhel-cdk.10.1.2.2.xip.io
> {quote}
> Deployment Config
> {noformat}
> {
> "kind" : "DeploymentConfig",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/deploymentconfigs/ghost",
> "uid" : "a7dafee5-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29849",
> "creationTimestamp" : "2016-04-16T11:45:02Z",
> "labels" : {"app" : "ghost"},
> "annotations" : {"openshift.io/generated-by" : "OpenShiftNewApp"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["ghost"],
> "from" : {
> "kind" : "ImageStreamTag",
> "namespace" : "my-ghost",
> "name" : "ghost:latest"
> },
> "lastTriggeredImage" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }
> }
> ],
> "replicas" : 1,
> "selector" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "template" : {
> "metadata" : {
> "labels" : {
> "app" : "ghost",
> "deploymentconfig" : "ghost"
> },
> "annotations" : {
> "openshift.io/container.ghost.image.entrypoint" : "[\"/entrypoint.sh\",\"npm\",\"start\"]",
> "openshift.io/generated-by" : "OpenShiftNewApp"
> }
> },
> "spec" : {
> "volumes" : [{"name" : "ghost-volume-1"}],
> "containers" : [{
> "name" : "ghost",
> "image" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "ports" : [{
> "containerPort" : 2368,
> "protocol" : "TCP"
> }],
> "volumeMounts" : [{
> "name" : "ghost-volume-1",
> "mountPath" : "/var/lib/ghost"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "status" : {
> "latestVersion" : 1,
> "details" : {"causes" : [{"type" : "ConfigChange"}]}
> }
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "kind" : "ImageStream",
> "apiVersion" : "v1",
> "metadata" : {
> "name" : "ghost",
> "namespace" : "my-ghost",
> "selfLink" : "/oapi/v1/namespaces/my-ghost/imagestreams/ghost",
> "uid" : "98a32494-03c8-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "29842",
> "creationTimestamp" : "2016-04-16T11:44:37Z",
> "annotations" : {"openshift.io/image.dockerRepositoryCheck" : "2016-04-16T11:44:37Z"}
> },
> "status" : {
> "dockerImageRepository" : "172.30.178.20:5000/my-ghost/ghost",
> "tags" : [{
> "tag" : "latest",
> "items" : [{
> "created" : "2016-04-16T11:44:37Z",
> "dockerImageReference" : "172.30.178.20:5000/my-ghost/ghost@sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8",
> "image" : "sha256:80590e45ef133a256906c454c8a20ae5e9b89773f6b452871ecf622001c836e8"
> }]
> }]
> }
> }
> {noformat}
> When following these steps in Eclipse, no deployment occurs. Going to the web console et clicking deploy on the Deployment, no image is found to deploy.
> {quote}
> - Clone https://github.com/burrsutter/cdk_helloworlds/
> - import java/wildflyswarm_helloworld as a Maven Project
> - Run a Maven build (Run As > Maven > package)
> - Edit Dockerfile: replace `FROM rhel7` with `FROM centos`
> - right click on Dockerfile > Run As > Docker Image build
> - Select `CDK Server Adapter at localhost` connection
> - Repository Name : hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm
> - from OpenShift explorer, create a fredo project
> - In OpenShift explorer, right-click the fredo project and Deploy Docker Image...
> - select hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm:latest for the image
> - swarm as resource name
> - click next
> - Deployment configuration & scalability page displays, click next
> - click add route button, click finish
> - resources are created, but no deployment happens
> {quote}
> Here are the resources created from Eclipse:
> Deployment Config
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/deploymentconfigs/swarm",
> "uid" : "2e9d1df4-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30206",
> "creationTimestamp" : "2016-04-16T12:10:17Z",
> "labels" : {"deploymentconfig" : "swarm"},
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {
> "strategy" : {
> "type" : "Rolling",
> "rollingParams" : {
> "updatePeriodSeconds" : 1,
> "intervalSeconds" : 1,
> "timeoutSeconds" : 600,
> "maxUnavailable" : "25%",
> "maxSurge" : "25%"
> }
> },
> "triggers" : [
> {"type" : "ConfigChange"},
> {
> "type" : "ImageChange",
> "imageChangeParams" : {
> "automatic" : true,
> "containerNames" : ["swarm"],
> "from" : {
> "kind" : "ImageStreamTag",
> "name" : "swarm:latest"
> }
> }
> }
> ],
> "replicas" : 1,
> "selector" : {"deploymentconfig" : "swarm"},
> "template" : {
> "metadata" : {"labels" : {"deploymentconfig" : "swarm"}},
> "spec" : {
> "containers" : [{
> "name" : "swarm",
> "image" : "fredo/swarm:latest",
> "ports" : [{
> "name" : "8080-tcp",
> "containerPort" : 8080,
> "protocol" : "TCP"
> }],
> "terminationMessagePath" : "/dev/termination-log",
> "imagePullPolicy" : "Always"
> }],
> "restartPolicy" : "Always",
> "terminationGracePeriodSeconds" : 30,
> "dnsPolicy" : "ClusterFirst"
> }
> }
> },
> "apiVersion" : "v1",
> "kind" : "DeploymentConfig"
> }
> {noformat}
> Image Stream
> {noformat}
> {
> "metadata" : {
> "name" : "swarm",
> "namespace" : "fredo",
> "selfLink" : "/oapi/v1/namespaces/fredo/imagestreams/swarm",
> "uid" : "2e42dfc8-03cc-11e6-82b7-525400ac6ae1",
> "resourceVersion" : "30202",
> "creationTimestamp" : "2016-04-16T12:10:16Z",
> "annotations" : {"openshift.io/generated-by" : "jbosstools-openshift"}
> },
> "spec" : {"dockerImageRepository" : "hub.openshift.rhel-cdk.10.1.2.2.xip.io/fredo/swarm"},
> "status" : {"dockerImageRepository" : "172.30.178.20:5000/fredo/swarm"},
> "apiVersion" : "v1",
> "kind" : "ImageStream"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22197) Icon in template Details of Local Template is not loaded for some templates file
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22197?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-22197:
-----------------------------------
Assignee: Jeff MAURY
> Icon in template Details of Local Template is not loaded for some templates file
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22197
> URL: https://issues.jboss.org/browse/JBIDE-22197
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: quickstart-template.json, screenshot-1.png
>
>
> {noformat}
> java.io.FileNotFoundException: /icons/apps/java.png
> at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:37)
> at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169)
> at java.net.URL.openConnection(Unknown Source)
> at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32)
> at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
> at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:219)
> at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283)
> at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:164)
> at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52)
> at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86)
> at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
> at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:214)
> at org.jboss.tools.openshift.internal.common.ui.ImageRepository.getImage(ImageRepository.java:85)
> at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:62)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.updateImage(TemplateDetailViews.java:106)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.onVisible(TemplateDetailViews.java:102)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:90)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:79)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews$1.handleValueChange(AbstractStackedDetailViews.java:73)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22197) Icon in template Details of Local Template is not loaded for some templates file
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22197?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22197:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Icon in template Details of Local Template is not loaded for some templates file
> --------------------------------------------------------------------------------
>
> Key: JBIDE-22197
> URL: https://issues.jboss.org/browse/JBIDE-22197
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Aurélien Pupier
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
> Attachments: quickstart-template.json, screenshot-1.png
>
>
> {noformat}
> java.io.FileNotFoundException: /icons/apps/java.png
> at org.eclipse.osgi.storage.url.bundleentry.Handler.findBundleEntry(Handler.java:37)
> at org.eclipse.osgi.storage.url.BundleResourceHandler.openConnection(BundleResourceHandler.java:169)
> at java.net.URL.openConnection(Unknown Source)
> at org.eclipse.osgi.storage.url.BundleURLConverter.toFileURL(BundleURLConverter.java:32)
> at org.eclipse.core.runtime.FileLocator.toFileURL(FileLocator.java:207)
> at org.eclipse.jface.resource.URLImageDescriptor.getFilePath(URLImageDescriptor.java:219)
> at org.eclipse.jface.resource.URLImageDescriptor.createImage(URLImageDescriptor.java:283)
> at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:164)
> at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:52)
> at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:86)
> at org.eclipse.jface.resource.ResourceManager.createImageWithDefault(ResourceManager.java:192)
> at org.eclipse.jface.resource.ImageRegistry.get(ImageRegistry.java:214)
> at org.jboss.tools.openshift.internal.common.ui.ImageRepository.getImage(ImageRepository.java:85)
> at org.jboss.tools.openshift.internal.ui.OpenShiftImages.getAppImage(OpenShiftImages.java:62)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.updateImage(TemplateDetailViews.java:106)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.TemplateDetailViews$TemplateDetailView.onVisible(TemplateDetailViews.java:102)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:90)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews.showView(AbstractStackedDetailViews.java:79)
> at org.jboss.tools.openshift.internal.common.ui.detailviews.AbstractStackedDetailViews$1.handleValueChange(AbstractStackedDetailViews.java:73)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
[~aileenc] - hmmm - is this what you downloaded?
{code}
ls -lt jboss-devstudio-is-installer-9.0.0.CR1a.jar
-rw-rw-r--. 1 pleacu pleacu 992043163 Apr 14 16:46 jboss-devstudio-is-installer-9.0.0.CR1a.jar
{code}
downloaded from
https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/jbos...
Are you running java 1.8? I'm on FC23 - which Fedora are you running?
Thkx!
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Aileen Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Aileen Cunningham commented on JBTIS-654:
-----------------------------------------
[~pleacu] I'm on fedora and only question I'm asked is to accept the licence. How do I specify to include Fuse?
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22201:
---------------------------------------
FYI, I was able to fix this by removing .vagrant in the Vagrantfile directory.
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3739) Docker connection does not work after cdk restart
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-3739?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-3739:
-------------------------------------
Stack trace from docker error:
{code}
com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:794)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
at org.eclipse.linuxtools.internal.docker.ui.commands.RefreshCommandHandler$2.run(RefreshCommandHandler.java:102)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.spotify.docker.client.DockerException: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:1141)
at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1072)
at com.spotify.docker.client.DefaultDockerClient.listImages(DefaultDockerClient.java:354)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listImages(DockerConnection.java:787)
... 3 more
Caused by: java.util.concurrent.ExecutionException: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306)
at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293)
at jersey.repackaged.com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:1070)
... 5 more
Caused by: javax.ws.rs.ProcessingException: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:517)
at org.glassfish.jersey.apache.connector.ApacheConnector$1.run(ApacheConnector.java:527)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at jersey.repackaged.com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293)
at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:49)
at jersey.repackaged.com.google.common.util.concurrent.AbstractListeningExecutorService.submit(AbstractListeningExecutorService.java:45)
at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:523)
at org.glassfish.jersey.client.ClientRuntime$1.run(ClientRuntime.java:169)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:320)
at org.glassfish.jersey.client.ClientRuntime$2.run(ClientRuntime.java:201)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.glassfish.jersey.apache.connector.ApacheConnector.apply(ApacheConnector.java:469)
... 20 more
Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: signature check failed
at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:352)
at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:260)
at sun.security.validator.Validator.validate(Validator.java:260)
at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324)
at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229)
at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124)
at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
... 39 more
Caused by: java.security.cert.CertPathValidatorException: signature check failed
at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135)
at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219)
at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140)
at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79)
at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292)
at sun.security.validator.PKIXValidator.doValidate(PKIXValidator.java:347)
... 45 more
Caused by: java.security.SignatureException: Signature does not match.
at sun.security.x509.X509CertImpl.verify(X509CertImpl.java:424)
at sun.security.provider.certpath.BasicChecker.verifySignature(BasicChecker.java:166)
at sun.security.provider.certpath.BasicChecker.check(BasicChecker.java:147)
at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:125)
... 50 more
{code}
> Docker connection does not work after cdk restart
> -------------------------------------------------
>
> Key: JBDS-3739
> URL: https://issues.jboss.org/browse/JBDS-3739
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: cdk, installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Labels: havoc
>
> When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work.
> This is caused by a bug in vagrant-service-manager 0.0.4:
> https://github.com/projectatomic/vagrant-service-manager/issues/80
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22201:
----------------------------------
Description:
Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
{code}
Error contacting OpenShift
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
{code}
When you actually copy&paste that url into a browser, you will get "ok".
This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
was:
Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
{code}
Error contacting OpenShift
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
{code}
When you actually copy&paste that url into a browser, you will get "ok".
This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora?).
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Martin Malina (JIRA)
Martin Malina created JBIDE-22201:
-------------------------------------
Summary: Error contacting OpenShift after CDK is started
Key: JBIDE-22201
URL: https://issues.jboss.org/browse/JBIDE-22201
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk, openshift
Affects Versions: 4.3.1.Final
Reporter: Martin Malina
Priority: Blocker
Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
{code}
Error contacting OpenShift
org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
{code}
When you actually copy&paste that url into a browser, you will get "ok".
This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora?).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months