July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22626: -------------------------------- Sprint: (was: devex #117 July 2016) > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM1 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22439: -------------------------------- Sprint: (was: devex #117 July 2016) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.1.AM2 > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours > Remaining Estimate: 1 day, 6 hours > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22621) Server adapter wizard: should be able to import projects to my workspace

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22621?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22621: -------------------------------- Sprint: (was: devex #117 July 2016) > Server adapter wizard: should be able to import projects to my workspace > ------------------------------------------------------------------------ > > Key: JBIDE-22621 > URL: https://issues.jboss.org/browse/JBIDE-22621 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.4.1.AM2 > > Attachments: no-workspace-project-exists.png > > > steps to reproduce: > # ASSERT: have empty workspace > # ASSERT: have at least 1 service in OpenShift > # EXEC: in OpenShift explorer: launch server adapter wizard from context menu of your service > Result: > The Eclipse project text field is erroring and nothing to select, since you have no project in your workspace yet. > !no-workspace-project-exists.png! > There's no way for the user to import a project from OpenShift to the workspace in this wizard. One has to close the wizard and head over to the import wizard first and get back. > Expected result: > I should have a link to the right of "Browse.." which allows me to import a project. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22442) Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22442?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22442: -------------------------------- Sprint: (was: devex #117 July 2016) > Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22442 > URL: https://issues.jboss.org/browse/JBIDE-22442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.x > > > When managing forwarding ports, select/unselecting the 'Find free local ports' checkbox makes the UI being unresponsive for several seconds and OS (Windows10 in my case) displaying 'Application not responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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: (was: devex #117 July 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: 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22645) Pre-select OpenShift 3 in New OpenShift Connection wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22645?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22645: -------------------------------- Sprint: (was: devex #117 July 2016) > Pre-select OpenShift 3 in New OpenShift Connection wizard > --------------------------------------------------------- > > Key: JBIDE-22645 > URL: https://issues.jboss.org/browse/JBIDE-22645 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Labels: openshift, openshift_v2, openshift_v3 > Fix For: 4.4.1.AM2 > > > Currently OS 2 is selected by default. We should pre-select OS 3 instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22433) Properties: Add Storage tab

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22433?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22433: -------------------------------- Sprint: (was: devex #117 July 2016) > Properties: Add Storage tab > --------------------------- > > Key: JBIDE-22433 > URL: https://issues.jboss.org/browse/JBIDE-22433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Fred Bricon > Assignee: Dmitry Bocharov > Labels: openshift_v3, properties > Fix For: 4.4.x > > Attachments: storage from web console.png > > > We should be able to display Persistent Volume (aka Storage) informations in the OpenShift properties. > Need to define the extent of the informations to display. At the very least, it should be the same as what the OpenShift Console provides. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22609: -------------------------------- Story Points: 3 > Provided wrong credentials, CDK server adapter says "started" even though it is not. > ------------------------------------------------------------------------------------ > > Key: JBIDE-22609 > URL: https://issues.jboss.org/browse/JBIDE-22609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.x > > > When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22651) No favicons for credentials domains on Mac or Windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22651?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22651: -------------------------------- Story Points: 6 > No favicons for credentials domains on Mac or Windows > ----------------------------------------------------- > > Key: JBIDE-22651 > URL: https://issues.jboss.org/browse/JBIDE-22651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Supposedly there should be favicons displayed for our jboss.org and redhat.com domains in the credentials preferences: > Preferences -> JBoss Tools -> Credentials > I only noticed this problem after reviewing JBIDE-22468 . And [~jkopriva] just showed me on his Linux box that he has the icons there. I don't have any icons on Mac or Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22635) Deprecate / Remove the Server Log View

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22635?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22635: -------------------------------- Story Points: 3 > Deprecate / Remove the Server Log View > -------------------------------------- > > Key: JBIDE-22635 > URL: https://issues.jboss.org/browse/JBIDE-22635 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM1 > Reporter: Rob Stryker > Assignee: Rob Stryker > > Deprecate and remove the Server Log View. > The Server Log View was originally designed to allow a custom "Error Log" to be filled with information that wasn't just "errors" but more like tracing what the server adapter was doing. > In it's original form, it held all status warnings and errors, and users never saw them. Eventually, we started also sending the status objects to the official Error Log, so users may see them. Once that happened, the Server Log view became completely redundant. It's only benefits were that it occasionally over-logged stuff that wasn't appropriate to send to the main error log... but it's API / extension points were kinda ugly, and it overall isn't very useful any longer. > Also, other server adapters have requested we remove the action at least, for their server types, since they never use the Server Log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 July 2016