[JBoss JIRA] (JBIDE-25593) VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25593?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-25593.
------------------------------------
Nothing for QE to verify here. Closing.
> VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25593
> URL: https://issues.jboss.org/browse/JBIDE-25593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Andre Dietisheim
> Fix For: 4.6.0.AM3
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> {noformat}
> java.lang.VerifyError: Bad type on operand stack
> Exception Details:
> Location:
> com/spotify/docker/client/DefaultDockerClient.copyContainer(Ljava/lang/String;Ljava/lang/String;)Ljava/io/InputStream; @43: invokevirtual
> Reason:
> Type 'com/fasterxml/jackson/databind/node/TextNode' (current frame, stack[2]) is not assignable to 'com/fasterxml/jackson/databind/JsonNode'
> Current Frame:
> bci: @43
> flags: { }
> locals: { 'com/spotify/docker/client/DefaultDockerClient', 'java/lang/String', 'java/lang/String', 'javax/ws/rs/client/WebTarget', 'com/fasterxml/jackson/databind/node/JsonNodeFactory' }
> stack: { 'com/fasterxml/jackson/databind/node/ObjectNode', 'java/lang/String', 'com/fasterxml/jackson/databind/node/TextNode' }
> Bytecode:
> 0x0000000: 2ab7 005a 1268 b900 5602 002b b900 5602
> 0x0000010: 0012 bfb9 0056 0200 4eb2 00c0 3a04 1904
> 0x0000020: b600 c112 c219 042c b600 c3b6 00c4 3a05
> 0x0000030: 2a12 6112 bd2d 2d04 bd00 5d59 03b2 00be
> 0x0000040: 53b9 005f 0200 1905 b800 63b7 0064 c000
> 0x0000050: bdb0
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:260)
> at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30)
> at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:186)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:202)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077)
> at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4032)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 |
> | org.eclipse.linuxtools.docker.core | 2.3.0.201704251823 | 2.3.0.201704251823 |
> | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 |
> | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 |
> | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 |
> | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 |
> | org.jboss.tools.openshift.cdk.server | 3.3.3.v20170510-2258 | 3.3.3.v20170510-2258 |
> Operating Systems:
> | Linux | 4.10.0 | 4.13.5.fc26 |
> | MacOSX | 10.11.6 | 10.12.3 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/591fb8d7e4b0dd...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25593) VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25593?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25593:
------------------------------------------
The tooling involved though, is 3.3.3.v20170510-2258, which is >1J old. The invloved class doesn't look the same either, l66 is where a parameter is defined:
{code}
64 public DockerClient getClient(
65 final IDockerConnectionSettings connectionSettings,
66 final IRegistryAccount registryAccount)
{code}
> VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25593
> URL: https://issues.jboss.org/browse/JBIDE-25593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Reporter: Automated Error Reporting Bot
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> {noformat}
> java.lang.VerifyError: Bad type on operand stack
> Exception Details:
> Location:
> com/spotify/docker/client/DefaultDockerClient.copyContainer(Ljava/lang/String;Ljava/lang/String;)Ljava/io/InputStream; @43: invokevirtual
> Reason:
> Type 'com/fasterxml/jackson/databind/node/TextNode' (current frame, stack[2]) is not assignable to 'com/fasterxml/jackson/databind/JsonNode'
> Current Frame:
> bci: @43
> flags: { }
> locals: { 'com/spotify/docker/client/DefaultDockerClient', 'java/lang/String', 'java/lang/String', 'javax/ws/rs/client/WebTarget', 'com/fasterxml/jackson/databind/node/JsonNodeFactory' }
> stack: { 'com/fasterxml/jackson/databind/node/ObjectNode', 'java/lang/String', 'com/fasterxml/jackson/databind/node/TextNode' }
> Bytecode:
> 0x0000000: 2ab7 005a 1268 b900 5602 002b b900 5602
> 0x0000010: 0012 bfb9 0056 0200 4eb2 00c0 3a04 1904
> 0x0000020: b600 c112 c219 042c b600 c3b6 00c4 3a05
> 0x0000030: 2a12 6112 bd2d 2d04 bd00 5d59 03b2 00be
> 0x0000040: 53b9 005f 0200 1905 b800 63b7 0064 c000
> 0x0000050: bdb0
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:260)
> at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30)
> at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:186)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:202)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077)
> at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4032)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 |
> | org.eclipse.linuxtools.docker.core | 2.3.0.201704251823 | 2.3.0.201704251823 |
> | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 |
> | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 |
> | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 |
> | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 |
> | org.jboss.tools.openshift.cdk.server | 3.3.3.v20170510-2258 | 3.3.3.v20170510-2258 |
> Operating Systems:
> | Linux | 4.10.0 | 4.13.5.fc26 |
> | MacOSX | 10.11.6 | 10.12.3 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/591fb8d7e4b0dd...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25593) VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25593?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25593:
------------------------------------------
as for automated error reporting this keeps happening. Latest occurrence is 2018/05/22
> VerifyError below CDKDockerUtility.<init> (thrown in DockerClientFactory.getClient)
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-25593
> URL: https://issues.jboss.org/browse/JBIDE-25593
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.2.Final
> Reporter: Automated Error Reporting Bot
> Fix For: 4.6.x
>
>
> The following problem was reported via the automated error reporting:
> Message: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> {noformat}
> java.lang.VerifyError: Bad type on operand stack
> Exception Details:
> Location:
> com/spotify/docker/client/DefaultDockerClient.copyContainer(Ljava/lang/String;Ljava/lang/String;)Ljava/io/InputStream; @43: invokevirtual
> Reason:
> Type 'com/fasterxml/jackson/databind/node/TextNode' (current frame, stack[2]) is not assignable to 'com/fasterxml/jackson/databind/JsonNode'
> Current Frame:
> bci: @43
> flags: { }
> locals: { 'com/spotify/docker/client/DefaultDockerClient', 'java/lang/String', 'java/lang/String', 'javax/ws/rs/client/WebTarget', 'com/fasterxml/jackson/databind/node/JsonNodeFactory' }
> stack: { 'com/fasterxml/jackson/databind/node/ObjectNode', 'java/lang/String', 'com/fasterxml/jackson/databind/node/TextNode' }
> Bytecode:
> 0x0000000: 2ab7 005a 1268 b900 5602 002b b900 5602
> 0x0000010: 0012 bfb9 0056 0200 4eb2 00c0 3a04 1904
> 0x0000020: b600 c112 c219 042c b600 c3b6 00c4 3a05
> 0x0000030: 2a12 6112 bd2d 2d04 bd00 5d59 03b2 00be
> 0x0000040: 53b9 005f 0200 1905 b800 63b7 0064 c000
> 0x0000050: bdb0
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:66)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:260)
> at org.eclipse.linuxtools.internal.docker.core.DefaultTCPConnectionSettingsProvider.getConnectionSettings(DefaultTCPConnectionSettingsProvider.java:30)
> at org.eclipse.linuxtools.internal.docker.core.DefaultDockerConnectionSettingsFinder.getKnownConnectionSettings(DefaultDockerConnectionSettingsFinder.java:265)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:60)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50)
> at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44)
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.<init>(CDKDockerUtility.java:29)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:104)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:186)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:202)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$1.run(Viewer.java:158)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:155)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2191)
> at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1728)
> at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1077)
> at org.eclipse.ui.navigator.CommonViewer.setSelection(CommonViewer.java:370)
> at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:383)
> at org.eclipse.wst.server.ui.internal.cnf.ServerDecoratorsHandler$1.run(ServerDecoratorsHandler.java:58)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4032)
> {noformat}
> Bundles:
> | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 |
> | org.eclipse.jface | 3.12.2.v20170113-2113 | 3.12.2.v20170113-2113 |
> | org.eclipse.linuxtools.docker.core | 2.3.0.201704251823 | 2.3.0.201704251823 |
> | org.eclipse.swt | 3.105.3.v20170228-0512 | 3.105.3.v20170228-0512 |
> | org.eclipse.ui | 3.108.1.v20160929-1045 | 3.108.1.v20160929-1045 |
> | org.eclipse.ui.navigator | 3.6.101.v20161006-1120 | 3.6.101.v20161006-1120 |
> | org.eclipse.wst.server.ui | 1.5.307.v201611072017 | 1.5.307.v201611072017 |
> | org.jboss.tools.openshift.cdk.server | 3.3.3.v20170510-2258 | 3.3.3.v20170510-2258 |
> Operating Systems:
> | Linux | 4.10.0 | 4.13.5.fc26 |
> | MacOSX | 10.11.6 | 10.12.3 |
> | Windows | 5.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://aer.ctrlflow.com/redhat/reviewers/#!/problems/591fb8d7e4b0dd...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25897 at 5/29/18 9:30 AM:
-------------------------------------------------------------------
Rejecting since this doesnt seem to be a bug but a general rule for OpenShift, where projects need unique names across users (see how you can reproduce this via Web-UI).
[~dgolovin] please reopen if you dont agree.
was (Author: adietish):
Rejecting since this doesnt seem to be a bug but a general rule for OpenShift, where projects need unique names across users (see how you can reproduce this via Web-UI).
> New Project validation uses wrong name space when there are two connections in OpenShift Explorer
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25897
> URL: https://issues.jboss.org/browse/JBIDE-25897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro, CDK 3.4.0-alpha.1
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
> Labels: explorer, new_project_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: project-already-exists.png, pyproject-error.gif
>
>
> !pyproject-error.gif!
> Prerequisites to reproduce the issue:
> 1. Start CDK/Minishift
> 2. Create second connection with different user name 'developer3' for example
> 3. Click hyper link in explorer to create new Project
> 4. Use name 'myproject'
> 5. ERROR:
> {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists
> Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-25897.
--------------------------------------
Resolution: Rejected
Rejecting since this doesnt seem to be a bug but a general rule for OpenShift, where projects need unique names across users (see how you can reproduce this via Web-UI).
> New Project validation uses wrong name space when there are two connections in OpenShift Explorer
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25897
> URL: https://issues.jboss.org/browse/JBIDE-25897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro, CDK 3.4.0-alpha.1
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
> Labels: explorer, new_project_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: project-already-exists.png, pyproject-error.gif
>
>
> !pyproject-error.gif!
> Prerequisites to reproduce the issue:
> 1. Start CDK/Minishift
> 2. Create second connection with different user name 'developer3' for example
> 3. Click hyper link in explorer to create new Project
> 4. Use name 'myproject'
> 5. ERROR:
> {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists
> Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25897:
-------------------------------------
Fix Version/s: 4.6.0.AM3
(was: 4.6.x)
> New Project validation uses wrong name space when there are two connections in OpenShift Explorer
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25897
> URL: https://issues.jboss.org/browse/JBIDE-25897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro, CDK 3.4.0-alpha.1
> Reporter: Denis Golovin
> Labels: explorer, new_project_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: project-already-exists.png, pyproject-error.gif
>
>
> !pyproject-error.gif!
> Prerequisites to reproduce the issue:
> 1. Start CDK/Minishift
> 2. Create second connection with different user name 'developer3' for example
> 3. Click hyper link in explorer to create new Project
> 4. Use name 'myproject'
> 5. ERROR:
> {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists
> Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-25897:
----------------------------------------
Assignee: Andre Dietisheim
> New Project validation uses wrong name space when there are two connections in OpenShift Explorer
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25897
> URL: https://issues.jboss.org/browse/JBIDE-25897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro, CDK 3.4.0-alpha.1
> Reporter: Denis Golovin
> Assignee: Andre Dietisheim
> Labels: explorer, new_project_wizard
> Fix For: 4.6.0.AM3
>
> Attachments: project-already-exists.png, pyproject-error.gif
>
>
> !pyproject-error.gif!
> Prerequisites to reproduce the issue:
> 1. Start CDK/Minishift
> 2. Create second connection with different user name 'developer3' for example
> 3. Click hyper link in explorer to create new Project
> 4. Use name 'myproject'
> 5. ERROR:
> {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists
> Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25897 at 5/29/18 9:27 AM:
-------------------------------------------------------------------
[~dgolovin] I'd tend to think that this is not a bug:
afaik namespaces for a server have to be unique across users, you cannot have 2 identical namespaces for 2 different users. To verify this do the following in CDK using the web-UI:
# EXEC: login as developer, create a project *camel-ose-springboot-xml* (or any name that you like)
# EXEC: logout, login again as admin
# EXEC: try to create the very same project (as you're now logged in as a different user) *camel-ose-springboot-xml*
Result:
You're prompted with an error telling you that the project already exists
!project-already-exists.png!
Resulting out of this is that the bug is not that you're prompted with an error telling you that the project already exists (which is actually true) but the fact the 2nd connection won't display the existing project. This bug is thus closely related or even duplicate to JBIDE-25756
was (Author: adietish):
[~dgolovin] I'd tend to think that this is more of a display error than a validation error:
afaik namespaces for a server have to be unique across users, you cannot have 2 identical namespaces for 2 different users. To verify this do the following in CDK using the web-UI:
# EXEC: login as developer, create a project *camel-ose-springboot-xml* (or any name that you like)
# EXEC: logout, login again as admin
# EXEC: try to create the very same project (as you're now logged in as a different user) *camel-ose-springboot-xml*
Result:
You're prompted with an error telling you that the project already exists
!project-already-exists.png!
Resulting out of this is that the bug is not that you're prompted with an error telling you that the project already exists (which is actually true) but the fact the 2nd connection won't display the existing project. This bug is thus closely related or even duplicate to JBIDE-25756
> New Project validation uses wrong name space when there are two connections in OpenShift Explorer
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25897
> URL: https://issues.jboss.org/browse/JBIDE-25897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.3.AM3
> Environment: Windows 10 Pro, CDK 3.4.0-alpha.1
> Reporter: Denis Golovin
> Labels: explorer, new_project_wizard
> Fix For: 4.6.x
>
> Attachments: project-already-exists.png, pyproject-error.gif
>
>
> !pyproject-error.gif!
> Prerequisites to reproduce the issue:
> 1. Start CDK/Minishift
> 2. Create second connection with different user name 'developer3' for example
> 3. Click hyper link in explorer to create new Project
> 4. Use name 'myproject'
> 5. ERROR:
> {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists
> Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25861) Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25861?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25861:
---------------------------------------
This seems pretty fine to me. Except, when I open the error view and check the log. I can spot error for docker daemon that cannot connect, which is alright, but message to this error in details contains: "Failed to connect to {0}". Seems like variable not being replaced in string for real value?
> Docker connection throws DockerTimeoutException with warning in error log when CDK is stopped
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-25861
> URL: https://issues.jboss.org/browse/JBIDE-25861
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker
> Affects Versions: 4.5.3.AM3
> Environment: Fedora 27 x86_64
> Reporter: Ondrej Dockal
> Assignee: Jeff Johnston
> Labels: upstream
> Fix For: 4.6.0.AM1
>
>
> After the docker connection is interrupted by force, there is written to console endless output from docker connection:
> {code}
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: Retrying request to {}->unix://localhost:80
> Mar 26, 2018 11:39:08 PM org.apache.http.impl.execchain.RetryExec execute
> INFO: I/O exception (java.io.IOException) caught when processing request to {}->unix://localhost:80: No such file or directory
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-26037) Deploy Docker Wizard: always prompts to create a new connection, does not preselect most recently used connection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26037?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26037:
-------------------------------------
Fix Version/s: 4.6.x
> Deploy Docker Wizard: always prompts to create a new connection, does not preselect most recently used connection
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26037
> URL: https://issues.jboss.org/browse/JBIDE-26037
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM2
> Reporter: Andre Dietisheim
> Labels: deploy_docker_wizard
> Fix For: 4.6.x
>
> Attachments: image-2018-05-23-22-51-38-221.png
>
>
> steps:
> # ASSERT: make sure that you have at least 1 connection to a OpenShift server defined
> # ASSERT: do some operations involving your existing connection (ex. open children for it in OpenShift Explorer)
> # EXEC: in "Docker Explorer": select an image and pick in the context menu "Deploy to OpenShift..."
> Result:
> You get prompted to create a <New Connection>
> !image-2018-05-23-22-51-38-221.png!
> If you unfold the "Connection" combo box to list all connections you discover your connection and can pick it instead of the suggested <New Connection>
> Expected result:
> The connection page shows up with the most recently connection preselected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months