December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21325) Connection wizard: trying to login with expired token causes 2nd, nested connection dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21325?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21325: ------------------------------------- Steps to Reproduce: # ASSERT: have connection with stored token ("Save token (could trigger secure storage login)" # ASSERT: have oc binary available in cmd line # EXEC: using *oc* in cmd line, login with the very same token that you're using in Eclipse (oc login --token=XXXX) and logout (this will expire your token) # EXEC: in Servers view context menu: New > Server # ASSERT: connection dialog shows up # EXEC: pick your connection (with the stored token) and hit Next Result: a 2nd, nested connection dialog shows up. !nested-2nd-conncetion-dialog.png! The very same can be achieved by using an invalid token. A 2nd dialog pops up. was: # ASSERT: have connection with stored token ("Save token (could trigger secure storage login)" # ASSERT: have oc binary available in cmd line # EXEC: using *oc* in cmd line, login with the very same token that you're using in Eclipse (oc login --token=XXXX) and logout (this will expire your token) # EXEC: in Servers view context menu: New > Server # ASSERT: connection dialog shows up # EXEC: pick your connection (with the stored token) and hit Next Result: a 2nd, nested connection dialog shows up. !nested-2nd-conncetion-dialog.png! > Connection wizard: trying to login with expired token causes 2nd, nested connection dialog > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21325 > URL: https://issues.jboss.org/browse/JBIDE-21325 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: connection_wizard, openshift_v3, respin-a > Fix For: 4.3.1.Beta1, 4.3.1.Beta2 > > Attachments: nested-2nd-conncetion-dialog.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21318: ------------------------------------- so the bug report seems to indicate OpenShift 2 servers have an OpenShift 3 label, that's surely wrong > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: server_adapter > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21321) Refresh does nothing on watch updates for deployment version of explorer view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21321?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21321: ------------------------------------- Fix Version/s: 4.3.1.Beta2 4.4.0.Alpha1 > Refresh does nothing on watch updates for deployment version of explorer view > ----------------------------------------------------------------------------- > > Key: JBIDE-21321 > URL: https://issues.jboss.org/browse/JBIDE-21321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > Watch and update is broken for new deployment view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19178: ------------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.x) > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21321) Refresh does nothing on watch updates for deployment version of explorer view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21321?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21321: ------------------------------------- Affects Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Refresh does nothing on watch updates for deployment version of explorer view > ----------------------------------------------------------------------------- > > Key: JBIDE-21321 > URL: https://issues.jboss.org/browse/JBIDE-21321 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > > Watch and update is broken for new deployment view -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19178) Explorer, Servers view: Add logical view to OpenShift v3 explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19178?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19178: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 > Explorer, Servers view: Add logical view to OpenShift v3 explorer > ----------------------------------------------------------------- > > Key: JBIDE-19178 > URL: https://issues.jboss.org/browse/JBIDE-19178 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Initial deployment view.png, Pipeline view mockup.bmml, Pipeline view mockup.png > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21327) [CDK] Check TLS_VERIFY flag after most recent openshift-vagrant cdk box updates

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21327?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21327: ------------------------------------- I verified it worked on OSX > [CDK] Check TLS_VERIFY flag after most recent openshift-vagrant cdk box updates > ------------------------------------------------------------------------------- > > Key: JBIDE-21327 > URL: https://issues.jboss.org/browse/JBIDE-21327 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.1.Beta1 > > > Changes to the most recent openshift-vagrant box require making sure the TLS_VERIFY flag is respected in the CDK server adapter tools when setting up the openshift connection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21318 at 12/15/15 3:03 PM: -------------------------------------------------------------------- I introduced the change in order to be able to see 2 things in the name (which wasnt possible so far) 1) OpenShift version (not needed so far, only v2 existed) 2) server 2) seems important to me since it's hard to know to what server which adapter will publish to. You only either know it by heart or have to look it up in the server editor, which I think is not very intuitive. [~fbricon] Thoughts? was (Author: adietish): I introduced the change in order to be able to see 2 things in the name (which wasnt possible so far) 1) OpenShift version (not needed so far, only v2 existed) 2) server 2) seems important to me since it's hard to know to what server which adapter will publish to. You only either know it by heart or have to look it up in the server editor, which I think is not very intuitive. Thoughts? > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: server_adapter > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21318) OpenShift 2 Server Adapter contains label "... at OpenShift 3"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21318?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21318: ------------------------------------------ I introduced the change in order to be able to see 2 things in the name (which wasnt possible so far) 1) OpenShift version (not needed so far, only v2 existed) 2) server 2) seems important to me since it's hard to know to what server which adapter will publish to. You only either know it by heart or have to look it up in the server editor, which I think is not very intuitive. Thoughts? > OpenShift 2 Server Adapter contains label "... at OpenShift 3" > --------------------------------------------------------------- > > Key: JBIDE-21318 > URL: https://issues.jboss.org/browse/JBIDE-21318 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Labels: server_adapter > > OpenShift 2 server adapters contains in name "... at OpenShift 3". E.g. "applicationName at OpenShift 3". This should be as it was earlier "... at OpenShift" or to distinguish between 2 and 3 we could use "... at OpenShift 2". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21170) Virtualbox could not be found by CDK adapter

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21170: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Virtualbox could not be found by CDK adapter > -------------------------------------------- > > Key: JBIDE-21170 > URL: https://issues.jboss.org/browse/JBIDE-21170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.1.Beta2 > > > After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this: > Server CDK Server Adapter at localhost failed to start. > Console: > {code} > The provider 'virtualbox' that was requested to back the machine > 'default' is reporting that it isn't usable on this system. The > reason is shown below: > Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed. > Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires > this to be available on the PATH. If VirtualBox is installed, please find the > `VBoxManage` binary and add it to the PATH environmental variable. > {code} > Along with this, there was an Unhandled event loop exception in the error view: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:520) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > Caused by: java.lang.NullPointerException > at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359) > at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162) > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 23 more > {code} > In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH. > Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped. > So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015