[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-24491:
------------------------------------
[~adietish] I don't think you have access to such asset in online OCP
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1112:
-----------------------------------
[~apodhrad] - Since the content is the same this doesn't warrant respining the release. I'd say stay with this for 10.3.0.GA.
> BPEL version was downgraded from 1.3.200 to 1.3.3
> -------------------------------------------------
>
> Key: JBTIS-1112
> URL: https://issues.jboss.org/browse/JBTIS-1112
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL, distribution
> Affects Versions: 10.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
> | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
> | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
> I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ]
Paul Leacu reassigned JBTIS-1112:
---------------------------------
Assignee: Paul Leacu
> BPEL version was downgraded from 1.3.200 to 1.3.3
> -------------------------------------------------
>
> Key: JBTIS-1112
> URL: https://issues.jboss.org/browse/JBTIS-1112
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL, distribution
> Affects Versions: 10.3.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
> | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
> | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
> I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24488) compilation error building Openshift Tools in master against Docker Tools 3.0 from Oxygen.0.M7
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24488?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov updated JBIDE-24488:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1507, https://github.com/jbosstools/jbosstools-openshift/pull/1509 (was: https://github.com/jbosstools/jbosstools-openshift/pull/1507)
> compilation error building Openshift Tools in master against Docker Tools 3.0 from Oxygen.0.M7
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24488
> URL: https://issues.jboss.org/browse/JBIDE-24488
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift, target-platform
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> Openshift Tools installation was failing with this error:
> {code}
> [p2.dir] !MESSAGE Cannot complete the install because one or more required items could not be found.
> [p2.dir] !MESSAGE Software being installed: JBoss OpenShift 3 Tools Developer Resources 3.4.0.v20170519-1022 (org.jboss.tools.openshift.feature.source.feature.group 3.4.0.v20170519-1022)
> [p2.dir] !MESSAGE Missing requirement: OpenShift 3 UI 3.4.0.v20170510-2205 (org.jboss.tools.openshift.ui 3.4.0.v20170510-2205) requires 'bundle org.eclipse.linuxtools.docker.core [2.1.0,3.0.0)' but it could not be found
> [p2.dir] !MESSAGE From: JBoss OpenShift 3 Tools 3.4.0.v20170519-1022 (org.jboss.tools.openshift.feature.feature.group 3.4.0.v20170519-1022)
> {code}
> So I pushed this PR:
> https://github.com/jbosstools/jbosstools-openshift/pull/1507
> And now it's failing with 9 compilation errors:
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:1.0.0:compile (default-compile) on project org.jboss.tools.openshift.ui: Compilation failure: Compilation failure:
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[30]
> [ERROR] import org.eclipse.linuxtools.docker.core.IDockerConnectionManagerListener2;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.linuxtools.docker.core.IDockerConnectionManagerListener2 cannot be resolved
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[58]
> [ERROR] implements IDeployImageParameters, IDockerConnectionManagerListener2, PropertyChangeListener {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] IDockerConnectionManagerListener2 cannot be resolved to a type
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[97]
> [ERROR] DockerConnectionManager.getInstance().addConnectionManagerListener(this);
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method addConnectionManagerListener(IDockerConnectionManagerListener) in the type DockerConnectionManager is not applicable for the arguments (DeployImageWizardModel)
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[103]
> [ERROR] DockerConnectionManager.getInstance().removeConnectionManagerListener(this);
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method removeConnectionManagerListener(IDockerConnectionManagerListener) in the type DockerConnectionManager is not applicable for the arguments (DeployImageWizardModel)
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[667]
> [ERROR] public void changeEvent(int event) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method changeEvent(int) of type DeployImageWizardModel must override or implement a supertype method
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[670]
> [ERROR] public void changeEvent(IDockerConnection connection, int event) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method changeEvent(IDockerConnection, int) of type DeployImageWizardModel must override or implement a supertype method
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[671]
> [ERROR] if ((event == ADD_EVENT)
> [ERROR] ^^^^^^^^^
> [ERROR] ADD_EVENT cannot be resolved to a variable
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/deployimage/DeployImageWizardModel.java:[672]
> [ERROR] || (event == REMOVE_EVENT)) {
> [ERROR] ^^^^^^^^^^^^
> [ERROR] REMOVE_EVENT cannot be resolved to a variable
> [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-openshift/plugins/org.jboss.tools.openshift.ui/src/org/jboss/tools/openshift/internal/ui/wizard/newapp/fromimage/ApplicationSourceFromImageModel.java:[55]
> [ERROR] public class ApplicationSourceFromImageModel
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The hierarchy of the type ApplicationSourceFromImageModel is inconsistent
> [ERROR] 9 problems (9 errors)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ERT-508) Docker Explorer shows error upon showing connection for the 1st time (after creation, eclipse startup, etc) [EBZ#517061]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-508:
---------------------------------------
Summary: Docker Explorer shows error upon showing connection for the 1st time (after creation, eclipse startup, etc) [EBZ#517061]
Key: ERT-508
URL: https://issues.jboss.org/browse/ERT-508
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Created attachment 268500
error upon the connection showing up in the "Docker Explorer"
steps to reproduce:
1. ASSERT: make sure that you have "Docker Explorer" opened
2. EXE: create a new docker connection (ex. to your local docker daemon)
Result:
The docker connection is then created and listed in the "Docker Explorer" but on the 1st appearance an error shows up:
java.lang.IllegalStateException: Entity input stream has already been closed.
at org.glassfish.jersey.message.internal.EntityInputStream.ensureNotClosed(EntityInputStream.java:228)
at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:854)
at org.glassfish.jersey.message.internal.InboundMessageContext.readEntity(InboundMessageContext.java:808)
at org.glassfish.jersey.client.ClientResponse.readEntity(ClientResponse.java:326)
at org.glassfish.jersey.client.InboundJaxrsResponse$1.call(InboundJaxrsResponse.java:115)
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:228)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:419)
at org.glassfish.jersey.client.InboundJaxrsResponse.runInScopeIfPossible(InboundJaxrsResponse.java:267)
at org.glassfish.jersey.client.InboundJaxrsResponse.readEntity(InboundJaxrsResponse.java:112)
at com.spotify.docker.client.DefaultDockerClient.message(DefaultDockerClient.java:2097)
at com.spotify.docker.client.DefaultDockerClient.propagate(DefaultDockerClient.java:2084)
at com.spotify.docker.client.DefaultDockerClient.request(DefaultDockerClient.java:2013)
at com.spotify.docker.client.DefaultDockerClient.listContainers(DefaultDockerClient.java:471)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.listContainers(DockerConnection.java:706)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.getContainers(DockerConnection.java:587)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.setState(DockerConnection.java:326)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.ping(DockerConnection.java:343)
at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:280)
at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:205)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
see docker-explorer-connection-error.png for the screenshot of the error
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1112?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1112:
-------------------------------------
Description:
BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
| Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
| Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
I didn't find any difference except the version definition.
was:
BPEL version was downgraded from 1.3.200 to 1.3.3.
| Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
| Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
I didn't find any difference except the version definition.
> BPEL version was downgraded from 1.3.200 to 1.3.3
> -------------------------------------------------
>
> Key: JBTIS-1112
> URL: https://issues.jboss.org/browse/JBTIS-1112
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPEL, distribution
> Affects Versions: 10.3.0.GA
> Reporter: Andrej Podhradsky
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> BPEL version was downgraded from 1.3.200 to 1.3.3. Namely, the feature org.jboss.tools.bpel.feature
> | Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
> | Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
> I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBTIS-1112) BPEL version was downgraded from 1.3.200 to 1.3.3
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1112:
----------------------------------------
Summary: BPEL version was downgraded from 1.3.200 to 1.3.3
Key: JBTIS-1112
URL: https://issues.jboss.org/browse/JBTIS-1112
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: BPEL, distribution
Affects Versions: 10.3.0.GA
Reporter: Andrej Podhradsky
Priority: Blocker
Fix For: 10.3.0.GA
BPEL version was downgraded from 1.3.200 to 1.3.3.
| Devstudio IS 10.3.0.CR2 | 1.3.200.Final-v20160331-1749-B19 |
| Devstudio IS 10.3.0.GA | 1.3.3.Final-v20170329-1943-B12 |
I didn't find any difference except the version definition.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24491:
------------------------------------------
[~jcantrill] [~jeffmaury] do you know how to look the address of the docker image registry on the online variant of OpenShift?
> CDK Server adapter: allow users to look up the address of the docker registry
> -----------------------------------------------------------------------------
>
> Key: JBIDE-24491
> URL: https://issues.jboss.org/browse/JBIDE-24491
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.Final
> Reporter: Andre Dietisheim
>
> if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
> When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
> Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
> It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
> I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-24491:
----------------------------------------
Summary: CDK Server adapter: allow users to look up the address of the docker registry
Key: JBIDE-24491
URL: https://issues.jboss.org/browse/JBIDE-24491
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.4.4.Final
Reporter: Andre Dietisheim
if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry.
When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address.
Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code}
It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line.
I dont know yet how to look it up for the OpenShift online variant though.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months