[JBoss JIRA] (JBIDE-21753) Explorer: connection name overlaps its icon until expanded with GTK3
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21753?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-21753.
------------------------------------
Resolution: Won't Fix
Agree with Fred. If it's reproducible only on Mars and GTK 3.16 then let's resolve it as "won't fix".
> Explorer: connection name overlaps its icon until expanded with GTK3
> --------------------------------------------------------------------
>
> Key: JBIDE-21753
> URL: https://issues.jboss.org/browse/JBIDE-21753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: gtk3
> Fix For: 4.3.1.CR1
>
> Attachments: connection.png, explorer-view-connections.png
>
>
> This is what the explorer looks like when I start up the tooling with GTK3:
> !connection.png|thumbnail!
> Expanding the connection will shift the text to its proper position.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21782) Adding EAP 7. ER6 server rises a warning on New runtime page
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-21782:
----------------------------------
Summary: Adding EAP 7. ER6 server rises a warning on New runtime page
Key: JBIDE-21782
URL: https://issues.jboss.org/browse/JBIDE-21782
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Screenshot: http://i.imgur.com/ObzrfQs.png
The warning is:
{noformat}
This server type expects a version of 6.1 but the server directory is of version 7.0.0.GA. This combination may cause critical errors. {noformat}
I guess it's because ER6 reports version "7.0.0.GA".
For example ER2 doesn't raise the warning (because it still reports as 7.0.0.Beta1).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21753) Explorer: connection name overlaps its icon until expanded with GTK3
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21753?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21753:
-------------------------------------
I'd rather leave it as-is if it occurs on only 1 gtk version
> Explorer: connection name overlaps its icon until expanded with GTK3
> --------------------------------------------------------------------
>
> Key: JBIDE-21753
> URL: https://issues.jboss.org/browse/JBIDE-21753
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Snjezana Peco
> Priority: Minor
> Labels: gtk3
> Fix For: 4.4.0.Alpha1
>
> Attachments: connection.png, explorer-view-connections.png
>
>
> This is what the explorer looks like when I start up the tooling with GTK3:
> !connection.png|thumbnail!
> Expanding the connection will shift the text to its proper position.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21742:
-------------------------------------
No, because I have the exact same problem of "No password provided" with my setup, which is bonkers.
> 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, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21776:
--------------------------------
Priority: Critical (was: Major)
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Priority: Critical
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21742:
-----------------------------------------------
Causes for exceptions may be many, and we show dialog with no exception details. So we should not hide any cause, but we do may hide the cause 'No password provided.', [~fbricon], would you agree?
> 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, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21776:
--------------------------------
Fix Version/s: 4.3.1.CR1
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21776) Cannot deploy docker image to OpenShift with manually entered details
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21776?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21776:
-----------------------------------
Assignee: Xavier Coulon
> Cannot deploy docker image to OpenShift with manually entered details
> ---------------------------------------------------------------------
>
> Key: JBIDE-21776
> URL: https://issues.jboss.org/browse/JBIDE-21776
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: docker, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: manually_filled.png, selected_image.png
>
>
> When deploying a docker image to OpenShift it is necessary to fill in namespace and image name at least (repo and tag is optional). Manually entering those values into the Deploy Image to OpenShift wizard does not work, although details are same as those filled automatically via selecting a docker image (click Search... button and select a specific one).
> There is no error in error log.
> Manually filled in details screenshot:
> !manually_filled.png!
> Automatically filled details via selecting a specific image screenshot:
> !selected_image.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21742) Secure storage of OpenShift 3 token does not work
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21742?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21742:
-------------------------------------
I'd rather keep that stacktrace for debugging purposes (see if I can get my keyring problem fixed someday)
> 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, 1 month
