[JBoss JIRA] (JBIDE-21829) Error while opening Eclipse with OpenShift Server Editor opened
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-21829.
-----------------------------------
Resolution: Cannot Reproduce Bug
Marking as {{resolved/cannot reproduce}} for now, since the problem is gone after I tried again today.
> Error while opening Eclipse with OpenShift Server Editor opened
> ---------------------------------------------------------------
>
> Key: JBIDE-21829
> URL: https://issues.jboss.org/browse/JBIDE-21829
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597
> !MESSAGE An internal error occurred during: "Setting connection, deploy project...".
> !STACK 0
> com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster
> at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133)
> at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256)
> at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This error also happens when the editor is closed at start-up and opened later on.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21845) Docker connection does not work with CDK build 2016-03-09
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21845?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-21845 at 3/17/16 7:21 AM:
----------------------------------------------------------------
[~akazakov], this has been verified as fixed in vagrant-service-manager 0.0.4 which has been released. As far as I understand it, this new version is included in CDK 2 Beta5.
So I believe this issue can be resolved, right [~hardy.ferentschik]?
was (Author: mmalina):
[~akazakov], this has been verified as fixed in vagrant-service-manager 0.0.4 which has been released. As far as I understand it, this new version is included in CDK 2 Beta5.
> Docker connection does not work with CDK build 2016-03-09
> ---------------------------------------------------------
>
> Key: JBIDE-21845
> URL: https://issues.jboss.org/browse/JBIDE-21845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-03-09 in JBDS 9.1.0.CR1 (build from 2 days ago).
> I start cdk, the docker connection is created, but it doesn't work:
> {code}
> 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:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> 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:780)
> ... 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:1506)
> 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:1488)
> ... 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}
> This looks similar to JBIDE-21733 . But in this case it doesn't work even from terminal:
> {code}
> $ eval "$(vagrant service-manager env docker)"
> $ docker ps
> An error occurred trying to connect: Get https://10.1.2.2:2376/v1.20/containers/json: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "example.com")
> {code}
> So yeah, this does not seem like the problem is on our site, but let's keep this JIRA for tracking anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21888) Pod is not created when docker image is deployed to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21888?page=com.atlassian.jira.plugi... ]
Marián Labuda resolved JBIDE-21888.
-----------------------------------
Resolution: Done
> Pod is not created when docker image is deployed to OpenShift
> -------------------------------------------------------------
>
> Key: JBIDE-21888
> URL: https://issues.jboss.org/browse/JBIDE-21888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21626) Pod is not created when docker image is deployed to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21626?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21626.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin build B233.
> Pod is not created when docker image is deployed to OpenShift
> -------------------------------------------------------------
>
> Key: JBIDE-21626
> URL: https://issues.jboss.org/browse/JBIDE-21626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21845) Docker connection does not work with CDK build 2016-03-09
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21845?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21845:
---------------------------------------
[~akazakov], this has been verified as fixed in vagrant-service-manager 0.0.4 which has been released. As far as I understand it, this new version is included in CDK 2 Beta5.
> Docker connection does not work with CDK build 2016-03-09
> ---------------------------------------------------------
>
> Key: JBIDE-21845
> URL: https://issues.jboss.org/browse/JBIDE-21845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Hardy Ferentschik
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> Today I tried cdk build 2016-03-09 in JBDS 9.1.0.CR1 (build from 2 days ago).
> I start cdk, the docker connection is created, but it doesn't work:
> {code}
> 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:787)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getImages(DockerConnection.java:750)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$5.run(DockerExplorerContentProvider.java:241)
> 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:780)
> ... 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:1506)
> 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:1488)
> ... 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}
> This looks similar to JBIDE-21733 . But in this case it doesn't work even from terminal:
> {code}
> $ eval "$(vagrant service-manager env docker)"
> $ docker ps
> An error occurred trying to connect: Get https://10.1.2.2:2376/v1.20/containers/json: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "example.com")
> {code}
> So yeah, this does not seem like the problem is on our site, but let's keep this JIRA for tracking anyway.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21888) Pod is not created when docker image is deployed to OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21888?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21888:
----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Pod is not created when docker image is deployed to OpenShift
> -------------------------------------------------------------
>
> Key: JBIDE-21888
> URL: https://issues.jboss.org/browse/JBIDE-21888
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21888) Pod is not created when docker image is deployed to OpenShift
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21888:
-------------------------------------
Summary: Pod is not created when docker image is deployed to OpenShift
Key: JBIDE-21888
URL: https://issues.jboss.org/browse/JBIDE-21888
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Assignee: Jeff Cantrill
Priority: Critical
Fix For: 4.3.1.CR1
When deploying a docker image to OpenShift via oc binary, pod where the image is supposed to run is created, together with service and router. But when deploying a docker image to OpenShift via OpenShift tools, no pod is created, only service and router. When using cli, pod is created later (what I noticed, there is different pull policy between creating from cli with "oc new-app docker-image" and creating from IDE).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21887) Enable port forwarding on a given pod and a given debug port
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21887?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21887:
------------------------------------------
cherry-picked into master
> Enable port forwarding on a given pod and a given debug port
> ------------------------------------------------------------
>
> Key: JBIDE-21887
> URL: https://issues.jboss.org/browse/JBIDE-21887
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
> The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
> If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21887) Enable port forwarding on a given pod and a given debug port
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-21887:
----------------------------------------
Summary: Enable port forwarding on a given pod and a given debug port
Key: JBIDE-21887
URL: https://issues.jboss.org/browse/JBIDE-21887
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Fred Bricon
Assignee: Xavier Coulon
Fix For: 4.3.1.CR1
Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21887) Enable port forwarding on a given pod and a given debug port
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21887?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21887:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Enable port forwarding on a given pod and a given debug port
> ------------------------------------------------------------
>
> Key: JBIDE-21887
> URL: https://issues.jboss.org/browse/JBIDE-21887
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug).
> The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration.
> If port forwarding is already enabled on the remote pod, then the current local debug port should be returned
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years