[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21789:
-------------------------------------
Description:
In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be.
!openshift-3-connections-listed.png!
If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
was:
In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
!openshift-3-connections-listed.png!
This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: openshift-3-connections-listed.png
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be.
> !openshift-3-connections-listed.png!
> If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21789:
-------------------------------------
Attachment: openshift-3-connections-listed.png
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: openshift-3-connections-listed.png
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> !openshift-3-connections-listed.png!
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21789:
-------------------------------------
Description:
In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
!openshift-3-connections-listed.png!
This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
was:
In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> !openshift-3-connections-listed.png!
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21789:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21789:
-------------------------------------
Summary: OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
Key: JBIDE-21789
URL: https://issues.jboss.org/browse/JBIDE-21789
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21789) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21789?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21789:
----------------------------------
Labels: openshift_v2 (was: )
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21789
> URL: https://issues.jboss.org/browse/JBIDE-21789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: openshift_v2
>
> In New Server wizard, when OpenShift 2 Server Adapter is chosen, next wizard page contains details of a new OS2 server adapter, such as connection, domain, project, application etc. In combo for a connection are not listed only OpenShift 2 connection but also OpenShift 3 connection, what should not be. If I select an OpenShift 3 connection on this wizard page, listed domains are those from previous OpenShift 2 connection.
> This has subsequent issue, which will be solved once there is no OS 3 connection listed in the combo. If there are no applications and I am trying to create a new application from this place (there is a link for it), it starts creation of a new application on a domain from OS2 connection although OS3 connection is selected in combo.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21787) New OpenShift Connection shells are not same
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21787?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21787:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> New OpenShift Connection shells are not same
> --------------------------------------------
>
> Key: JBIDE-21787
> URL: https://issues.jboss.org/browse/JBIDE-21787
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Labels: connection_wizard
> Fix For: 4.3.1.CR1
>
>
> New Connection wizard opened via link in OpenShift Explorer view is not same as the one opened via tool item. The one opened via link available while there is no connection does not contain title. The other one has title "New OpenShift Connection". They both could have same title.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21737) Error while selecting a project in the OpenShift Explorer view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21737?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21737:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Error while selecting a project in the OpenShift Explorer view
> --------------------------------------------------------------
>
> Key: JBIDE-21737
> URL: https://issues.jboss.org/browse/JBIDE-21737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> I have the following exception *many times* in the console when I select a project in the OpenShift Explorer view:
> {code}
> org.eclipse.core.commands.common.NotDefinedException: Cannot get the parent identifier from an undefined context. org.jboss.tools.openshift.explorer.context.connection
> at org.eclipse.core.commands.contexts.Context.getParentId(Context.java:197)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.getLevel(ContextSet.java:49)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:38)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:1)
> at java.util.TimSort.binarySort(TimSort.java:292)
> at java.util.TimSort.sort(TimSort.java:217)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1454)
> at java.util.Collections.sort(Collections.java:175)
> at org.eclipse.e4.ui.bindings.internal.ContextSet.<init>(ContextSet.java:77)
> at org.eclipse.e4.ui.bindings.internal.BindingTableManager.createContextSet(BindingTableManager.java:90)
> at org.eclipse.e4.ui.bindings.internal.BindingServiceImpl.setContextIds(BindingServiceImpl.java:177)
> at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:90)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
> at org.eclipse.e4.ui.internal.services.ContextContextService.activateContext(ContextContextService.java:56)
> at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:170)
> at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:102)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$Contexts.activate(OpenShiftExplorerView.java:201)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$OpenShiftExplorerContextsHandler$2.selectionChanged(OpenShiftExplorerView.java:187)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> 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:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:5045)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5432)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2066)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2571)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2034)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21761:
------------------------------------------
[~jcantrill] I remember you mentioning this feature where a port can be a numeric or named value. Can you confirm?
> Port mapping validation is not correct
> --------------------------------------
>
> Key: JBIDE-21761
> URL: https://issues.jboss.org/browse/JBIDE-21761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: validation_msg.png
>
>
> In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
> !validation_msg.png!
> There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21761:
-------------------------------------
Fix Version/s: 4.3.1.CR1
> Port mapping validation is not correct
> --------------------------------------
>
> Key: JBIDE-21761
> URL: https://issues.jboss.org/browse/JBIDE-21761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: validation_msg.png
>
>
> In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image.
> !validation_msg.png!
> There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month