June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22595: ------------------------------------- Sprint: devex #116 June 2016 > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22595: ---------------------------------------- Assignee: Andre Dietisheim > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22595: ------------------------------------- Labels: connection_wizard openshift_v3 (was: ) > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20753) Text flickering when selecting server types in New Server wizard

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20753?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20753: --------------------------------------- I tried again now in both devstudio 10 and Eclipse Neon RC2 and I can still see it. So it's really weird you can't see it. > Text flickering when selecting server types in New Server wizard > ---------------------------------------------------------------- > > Key: JBIDE-20753 > URL: https://issues.jboss.org/browse/JBIDE-20753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Martin Malina > Assignee: Snjezana Peco > Labels: regression > Fix For: 4.4.x > > > When you open the New Server wizard and select a server type, There will be some elements rendered for a fraction of a second. It's Server Runtime Environment and a dropdown menu - it will disappear again, but it's not nice to see something quickly appear and disappear again. You can keep selecting server types and it will keep happening. All of this is on the first page of the dialog. > I checked and this did not happen in Beta2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-753) JBDSIS discovery composites wrong for EA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-753?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-753. ----------------------------------- Verified the site at https://devstudio.redhat.com/9.0/stable/updates/integration-stack/discove... as well as verified the installation from Red Hat Central > JBDSIS discovery composites wrong for EA > ---------------------------------------- > > Key: JBTIS-753 > URL: https://issues.jboss.org/browse/JBTIS-753 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > JBDSIS discovery composites wrong for early access -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-22580: ---------------------------------- Component/s: docker > Deploy Docker Image wizard: Cannot push already tagged image to docker registry > ------------------------------------------------------------------------------- > > Key: JBIDE-22580 > URL: https://issues.jboss.org/browse/JBIDE-22580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace > {code}Failed to push the selected Docker image into OpenShift registry > org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21936) Disable livereload context menu on stopped server modules

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21936?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21936: -------------------------------- Sprint: devex #116 June 2016 > Disable livereload context menu on stopped server modules > --------------------------------------------------------- > > Key: JBIDE-21936 > URL: https://issues.jboss.org/browse/JBIDE-21936 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Dmitry Bocharov > Fix For: 4.4.x > > > Similar to JBIDE-21517, but this time the server is running, but the deployed project is not. Both the context menu for show in via livereload and the quick access command are enabled for a stopped module. And they just open a browser tab with 404 - not found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21936) Disable livereload context menu on stopped server modules

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21936?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21936: ----------------------------------- Assignee: Dmitry Bocharov (was: Xavier Coulon) > Disable livereload context menu on stopped server modules > --------------------------------------------------------- > > Key: JBIDE-21936 > URL: https://issues.jboss.org/browse/JBIDE-21936 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: livereload > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Dmitry Bocharov > Fix For: 4.4.x > > > Similar to JBIDE-21517, but this time the server is running, but the deployed project is not. Both the context menu for show in via livereload and the quick access command are enabled for a stopped module. And they just open a browser tab with 404 - not found. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21877: -------------------------------- Sprint: devex #116 June 2016 > 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: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21877) Connection wizard: Make error message shown in OpenShift Explorer for outdated token more user friendly

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21877?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-21877: ---------------------------------- Assignee: Jeff MAURY (was: Viacheslav Kabanovich) > 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 > > > 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, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016