[JBoss JIRA] (JBIDE-21425) Server adapter wizard: Finish button should be disabled in page which contains connection selection
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21425?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-21425:
----------------------------------------
Assignee: (was: Andre Dietisheim)
> Server adapter wizard: Finish button should be disabled in page which contains connection selection
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21425
> URL: https://issues.jboss.org/browse/JBIDE-21425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2, 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
>
> In server adapter wizard on wizard page where selection of a connection is performed, the Finish button is enabled. This should not be possible, because although connection is selected but service, eclipse project and paths are not filled in. Hitting finish button in this stage leads to a new server adapter, which does not do anything and its linked to nothing, because details are empty.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21742.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> Secure storage of OpenShift 3 token does not work
> -------------------------------------------------
>
> Key: JBIDE-21742
> URL: https://issues.jboss.org/browse/JBIDE-21742
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: connection, openshift_v3, security_domain
> Fix For: 4.3.1.CR1
>
> Attachments: SecureStorageAccessFailure.png
>
>
> When I have already user secure storage in another session (password is set) and I fill in valid token and check checkbox to store token in secure storage, confirmation dialog of secure storage is shown upon hitting Finish button. Upon filling invalid secure storage password for first time, dialog is invoked again to enter password. After second filling of invalid password for secure storage, it looks like it passed - no other prompt nor error dialog (just in error log see stack trace) and even in Connection dialog (opened via Edit context menu item on the connection) is checkbox for secure storage checked, what is wrong, because it is not stored (checked secure storage preference page and its content and also after restart of eclipse it was not stored).
> {code}
> org.jboss.tools.openshift.internal.common.core.security.SecureStoreException: Could not store value token: iQKo-5jRkMeaegCi3mljsFsAXhNaogmzwaKeaQNUAxc
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:104)
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.put(SecureStore.java:57)
> at org.jboss.tools.openshift.core.connection.Connection.saveOrClear(Connection.java:187)
> at org.jboss.tools.openshift.core.connection.Connection.save(Connection.java:159)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:207)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:424)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:368)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:355)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:60)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:95)
> at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:167)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.eclipse.equinox.security.storage.StorageException: No password provided.
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getModulePassword(SecurePreferencesRoot.java:304)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesRoot.getPassword(SecurePreferencesRoot.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferences.put(SecurePreferences.java:224)
> at org.eclipse.equinox.internal.security.storage.SecurePreferencesWrapper.put(SecurePreferencesWrapper.java:110)
> at org.jboss.tools.openshift.internal.common.core.security.SecureStore.store(SecureStore.java:102)
> ... 11 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21764) Duplicates of environment variables should be forbidden
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21764?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21764.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> Duplicates of environment variables should be forbidden
> -------------------------------------------------------
>
> Key: JBIDE-21764
> URL: https://issues.jboss.org/browse/JBIDE-21764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> On 2nd wizard page of Deploy docker image is a table containing env. variables passed to OpenShift deployment config when docker image is deployed. Currently it is allowed to create duplicates of environment variables (more variables with same name), but only the last one is processed = it is passed to deployment config. E.g. I created env. vars. envvar1=val1 and envvar1=val2, but in deployment config only val2 is located. We should forbidden created duplicates of environment variables with same name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21787) New OpenShift Connection shells are not same
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21787?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21787.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> 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, 4.4.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21802:
---------------------------------------
I am noticing some performance issues. Sometimes when I type it freezes for a moment/few seconds and then continues to work. Can't exactly tell what is causing those delay, but from user point of view it is really annoying. Could you please look at it?
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21802
> URL: https://issues.jboss.org/browse/JBIDE-21802
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21790) OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21790?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21790.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> OpenShift 3 connections are listed in Create OpenShift 2 server adapter wizard
> ------------------------------------------------------------------------------
>
> Key: JBIDE-21790
> URL: https://issues.jboss.org/browse/JBIDE-21790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> 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
[JBoss JIRA] (JBIDE-21813) Delete of OpenShift application via server adapter is disabled
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21813?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21813.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> Delete of OpenShift application via server adapter is disabled
> --------------------------------------------------------------
>
> Key: JBIDE-21813
> URL: https://issues.jboss.org/browse/JBIDE-21813
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2
> Fix For: 4.3.1.CR1
>
> Attachments: video.ogg-1.ogv
>
>
> Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21825) Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21825?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21825.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> Application wizard: Duplicate templates in different OpenShift projects are not distinguishable from each other
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21825
> URL: https://issues.jboss.org/browse/JBIDE-21825
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: screenshot-1.png, TemplateLableWithNamespace.png
>
>
> New app from template should allow a user to pick templates form either the 'OpenShift' project or their own and they should be able to tell the difference. The attached screen show displays the same template twice but actually, one is in the openshift project and the other is in the 'hello-world'
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21842) OpenShift server adpter editor: link 'Open launch configuration' throws exception
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21842?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21842.
---------------------------------
Verified on nightly build of JBT with OpenShift plugin version 3.1.0.CR1-v20160310-0336-B219.
> OpenShift server adpter editor: link 'Open launch configuration' throws exception
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-21842
> URL: https://issues.jboss.org/browse/JBIDE-21842
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v2, server_adapter_editor
> Fix For: 4.3.1.CR1
>
> Attachments: ErrorAtEditLaunchConfig.png
>
>
> There is no launch configuration tab groups bound to the openshift launch type.
> As the result, an exception is caught at opening 'Edit Configuration' wizard. The exception is not logged, but user has to click OK on two successive Error and Problem occurred message dialogs and finally gets the wizard with empty Name input and error message 'A name is required for the configuration'.
> This user unfriendly behaviour may be considered an upstream issue, but the workaround is just to bind an empty list of tab groups.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years