[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22613 at 6/20/16 10:13 AM:
--------------------------------------------------------------------
[~jeffmaury] On what OpenShift instance do you have both OAuth and Basic working? How can I reproduce this?
was (Author: adietish):
[~jeffmaury] On what OpenShift instance do you have both OAuth and Basic working?
> Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22613
> URL: https://issues.jboss.org/browse/JBIDE-22613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Labels: connection, connection_wizard, openshift_v3
> Fix For: 4.4.1.S117
>
>
> If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22613:
-------------------------------------
Summary: Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid (was: When a connection is configured with a stored token, switching back with basic will fail if token is invalid)
> Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22613
> URL: https://issues.jboss.org/browse/JBIDE-22613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Labels: connection, connection_wizard, openshift_v3
> Fix For: 4.4.1.S117
>
>
> If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-22611:
------------------------------------
It appears to be a TP version error of involving org.eclipse.egit.ui.smartimport - see:
https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
https://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/...
> target platform validation fails to detect duplicate IUs
> --------------------------------------------------------
>
> Key: JBIDE-22611
> URL: https://issues.jboss.org/browse/JBIDE-22611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.S116
>
>
> Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example:
> {code}
> [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933)
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022)
> BUILD FAILED
> {code}
> But this is not the same error that Paul Leacu recently reported:
> {code}
> > [ERROR] Resolution failed:
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code}
> So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is.
> Either way, we need to make these problems more visible so they're caught sooner.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21877:
------------------------------------------
[~jeffmaury] Even though I have the very same symptoms with empty token text field if the token expires I dont have the NPE that you're experiencing. What points to OpenShift being the culprit in this for you?
Out of my memories I know that there are several different ProxyAutenticators in Eclipse and it highly depends on your setup which one is active for you. Given that this is upstream (assuming that our tooling is not at fault - what I suspect from reading the above) I would file an Eclipse bugzillla and reject this jira.
> Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: screenshot-1.png
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21877:
------------------------------------------
[~scabanovich] weird, I cannot access https://bugs.eclipse.org/bugs/show_bug.cgi?id=487975, I am told that I am not authorized. I dont think that we should implement workarounds if they're not really required. I especially think that we should not fiddle with the system in the openshift-restclient-java. The issue seems Eclipse related, the client thus shouldnt care about it since it may be used outside Eclipse.
> Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21877
> URL: https://issues.jboss.org/browse/JBIDE-21877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: screenshot-1.png
>
>
> When I am trying to connect to OpenShift connection with outdated token stored in secure storage, an error tree item is shown in OpenShift Explorer under the connection. Erro tree item is "java.lang.NullPointerException", but it could be something more user friendly such as "Expired credentials" or the one we are already using in other scenarious - You must obtain an API token by .... Following stack trace is in error log
> {code}
> There was an error retrieving children in the OpenShift explorer
> java.lang.NullPointerException
> at org.eclipse.epp.internal.mpc.core.util.ProxyHelper$ProxyAuthenticator.getPasswordAuthentication(ProxyHelper.java:124)
> at java.net.Authenticator.requestPasswordAuthentication(Authenticator.java:317)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getSystemCreds(SystemDefaultCredentialsProvider.java:92)
> at org.apache.http.impl.client.SystemDefaultCredentialsProvider.getCredentials(SystemDefaultCredentialsProvider.java:113)
> at com.openshift.internal.restclient.authorization.OpenShiftCredentialsProvider.getCredentials(OpenShiftCredentialsProvider.java:69)
> at org.apache.http.impl.client.AuthenticationStrategyImpl.select(AuthenticationStrategyImpl.java:184)
> at org.apache.http.impl.client.TargetAuthenticationStrategy.select(TargetAuthenticationStrategy.java:43)
> at org.apache.http.impl.auth.HttpAuthenticator.handleAuthChallenge(HttpAuthenticator.java:154)
> at org.apache.http.impl.execchain.MainClientExec.needAuthentication(MainClientExec.java:557)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:275)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContext(AuthorizationClient.java:99)
> at com.openshift.internal.restclient.DefaultClient.getContext(DefaultClient.java:504)
> at org.jboss.tools.openshift.core.connection.Connection.authorize(Connection.java:236)
> at org.jboss.tools.openshift.core.connection.Connection.connect(Connection.java:226)
> at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:445)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:389)
> at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:376)
> at org.jboss.tools.openshift.internal.ui.models.OpenShiftProjectCache.getProjectsFor(OpenShiftProjectCache.java:59)
> at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:93)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22611) target platform validation fails to detect duplicate IUs
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22611?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-22611:
----------------------------------------
This error seems most likely caused by the version of Eclipse IDE used in order to validate the TP not being the same than the content of the TP itself. As far as I understand, this kind of error are caused "by design" of installing all content from a TP even if we're not going to install those specific versions directly. They are basically false-positive IMO, and checking installation so early reports errors that actually do not affect our delivery.
> target platform validation fails to detect duplicate IUs
> --------------------------------------------------------
>
> Key: JBIDE-22611
> URL: https://issues.jboss.org/browse/JBIDE-22611
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.1.S116
>
>
> Recently, I added the Jenkins Text Finder to the target platform matrix job so that when bad things happen in the log, the build is shown in yellow instead of having the bad things ignored behind a blue ball. For example:
> {code}
> [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160603-1933 (org.eclipse.m2e.model.edit 1.7.0.20160603-1933)
> [p2.dir] !MESSAGE Maven Project Model Edit Bundle 1.7.0.20160531-2022 (org.eclipse.m2e.model.edit 1.7.0.20160531-2022)
> BUILD FAILED
> {code}
> But this is not the same error that Paul Leacu recently reported:
> {code}
> > [ERROR] Resolution failed:
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2
> > [ERROR] Software being installed: org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r
> > [ERROR] Only one of the following can be installed at once: [org.eclipse.egit.ui.smartimport 4.4.0.201606070830-r, org.eclipse.egit.ui.smartimport 4.4.0.201606011500-rc2]{code}
> So either we have multiple instances of multiple versions of the same IU, or he's doing a different installation than the TP verification step is.
> Either way, we need to make these problems more visible so they're caught sooner.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22578) Publishing sometimes recursively deletes parent to deploy directory
by Daniel Atallah (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22578?page=com.atlassian.jira.plugi... ]
Daniel Atallah commented on JBIDE-22578:
----------------------------------------
With 4.3.1.Final and the {{.options}} file specified above and {{\-debug}} CLI argument, there isn't any additional output at the time the issue happens- there's a time gap in the logs and then the same error:
{noformat}
!ENTRY org.eclipse.wst.server.core 4 0 2016-06-15 17:29:31.668
!MESSAGE The server cannot start because it is currently starting or stopping. Wait for the current operation to complete.
!ENTRY org.jboss.ide.eclipse.as.core 4 0 2016-06-15 17:29:47.643
!MESSAGE Unable to retrieve a list of remote deployment scanners
!ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-15 17:36:16.496
!MESSAGE Incremental publish failed for module MobileWeb
!SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-15 17:36:16.496
!MESSAGE Could not delete C:/lean2/development/tms/bilbo. May be locked by another process.
{noformat}
If there's a way for me to test with a build containing the additional logging, please let me know.
> Publishing sometimes recursively deletes parent to deploy directory
> -------------------------------------------------------------------
>
> Key: JBIDE-22578
> URL: https://issues.jboss.org/browse/JBIDE-22578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.1.Final
> Environment: Eclipse Mars.2 Release (4.5.2)
> Java 1.8.0_91
> Windows 7 64-bit
> JBoss EAP 6.4.0
> Reporter: Daniel Atallah
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.1.S116
>
> Attachments: jboss_deployment.jpg, servers.xml
>
>
> For a number of weeks we've had a number of occurrences where a eclipse workspace will get corrupted due to the deletion of all files in it.
> It seems to have started happening at the time we updated to the 4.3.1 JBoss Tools from the 4.3.0 JBoss Tools.
> We've been able to track the process doing the deleting to the Eclipse process by using Sysinternals Process Monitor tool (https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx).
> Our workspaces are structured as follows:
> {noformat}
> WORKSPACEROOT=$DEVROOT\workspacename
> # Custom deploy folder (as specified in the "Deployment" settings for the configured "Red Hat JBoss Enterprise Application Platform 6.1+") Server
> $WORKSPACEROOT\deploy
> # Version Control (Mercurial) working directory containing various Eclipse projects that get published to the Server by the tooling
> $WORKSPACEROOT\src
> # value specified as a "jboss.server.data.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/data
> # value specified as a "jboss.server.temp.dir" property in the Server launch configuration VM arguments
> $WORKSPACEROOT/server/tmp
> {noformat}
> The Server is configured to "Automatically publish when resources change".
> What we're seeing is that occasionally when the Server is running and the Mercurial working copy receives updates, the Incremental Publishing that results from these updates somehow tries to recursively delete $WORKSPACEROOT.
> The eclipse log includes the following:
> {noformat}
> !ENTRY org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problems occurred refreshing resources
> !SUBENTRY 1 org.eclipse.core.resources 4 1 2016-06-07 16:05:57.795
> !MESSAGE Problem finding next change, code: 5
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298244 2016-06-07 16:06:09.207
> !MESSAGE Incremental publish failed for module $MODULENAME
> !SUBENTRY 1 org.jboss.ide.eclipse.as.wtp.core 4 1644298251 2016-06-07 16:06:09.207
> !MESSAGE Could not delete $WORKSPACEROOT. May be locked by another process.
> {noformat}
> Any idea what might be happening?
> Is there some debug logging we can enable to get better visibility to what's going on?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months