February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21710) [CDK] replace calls to adbinfo plugin with service-manager plugin

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21710?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21710: -------------------------------- Component/s: (was: openshift) > [CDK] replace calls to adbinfo plugin with service-manager plugin > ----------------------------------------------------------------- > > Key: JBIDE-21710 > URL: https://issues.jboss.org/browse/JBIDE-21710 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk, server > Reporter: Navid Shaikh > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > vagrant-service-manager plugin [1] is a successor for vagrant-adbinfo plugin [2]. > All further development towards displaying and configuring provider [docker, openshift, kubernetes, etc] information from ADB / CDK, will happen in vagrant-service-manager plugin. > Equivalent functionality from vagrant-adbinfo plugin is now ported to vagrant-service-manager plugin. > To display docker connection information from vagrant box, > using adbinfo > ``` > $ vagrant adbinfo > ``` > using service-manager > ``` > $vagrant service-manager env docker > ``` > Kindly update the tooling which are using adbinfo plugin with service-manager command. > Note: adbinfo plugin has a dependency on `scp` / `pscp` utility for copying certs. service-manager plugin does not need `scp` / `pscp` utility to copy the certs. > [1] https://github.com/projectatomic/vagrant-service-manager > [2] https://github.com/projectatomic/vagrant-adbinfo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21319) CDK start fails for no reason - it's actually running

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21319?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21319: -------------------------------- Component/s: cdk (was: openshift) > CDK start fails for no reason - it's actually running > ----------------------------------------------------- > > Key: JBIDE-21319 > URL: https://issues.jboss.org/browse/JBIDE-21319 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > I just tried to start the CDK adapter. > After it all started, Eclipse showed me an error window saying: > {code} > Server cdk-v2 CDK Server failed to start. > {code} > The server views shows [Stopped], but running "vagrant status" in command line shows it's running. > I know this is not much information, but really I don't have anything else. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21290: -------------------------------- Component/s: cdk (was: openshift) > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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: -------------------------------- Component/s: cdk (was: openshift) > 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: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.1.CR1 > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21364) [CDK] Change how fetching environment vars via adbinfo works

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21364?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21364: -------------------------------- Component/s: cdk (was: server) (was: openshift) > [CDK] Change how fetching environment vars via adbinfo works > ------------------------------------------------------------ > > Key: JBIDE-21364 > URL: https://issues.jboss.org/browse/JBIDE-21364 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.3.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Current behavior runs adbinfo directly via runtime.exec(etc). > Investigate upstream solutions as shown here: https://github.com/eclipse/linuxtools/blob/master/containers/org.eclipse.... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21634: ------------------------------------------ postponing this non-critical issue since we already have plenty of items to fullfill 4.3.0.CR1 > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (server) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21727: -------------------------------- Fix Version/s: 4.4.x (was: 4.3.1.CR1) > add OpenShift server adapter to downloadable WTP server adapters > ---------------------------------------------------------------- > > Key: JBIDE-21727 > URL: https://issues.jboss.org/browse/JBIDE-21727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.4.x > > > We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too. > Anything preventing us from doing so ? > Is there a workflow from New server that helps users to create openshift connection etc. ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21634) Explorer, Properties: Allow a user to scale their deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21634?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21634: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Explorer, Properties: Allow a user to scale their deployment > ------------------------------------------------------------ > > Key: JBIDE-21634 > URL: https://issues.jboss.org/browse/JBIDE-21634 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3, properties > Fix For: 4.4.0.Alpha1 > > > The web and cli allows a user to scale their deployments, which is only possible now in Eclipse by editing the replicationcontroller. Add UI to facilitate scaling. Scaling should be allowed in some sort of context menu when selecting any of: > 1. deployment (replication controller) > 2. eclipse view of a deployment (server) -> walk back to the currrent deployment > 3. pod -> walk back to the current deployment > updating 'spec.replicas' causes a new pods to spin up -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20513) tricky to login to openshift when token expires

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20513?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-20513: ---------------------------------------- Assignee: Andre Dietisheim > tricky to login to openshift when token expires > ----------------------------------------------- > > Key: JBIDE-20513 > URL: https://issues.jboss.org/browse/JBIDE-20513 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.1.CR1 > > > I logged in with token. > 24hrs later I start eclipse and expand the connection in explorer > expecting to just login. > Here is what happens instead: > a) info message (not error) is logged to error log hiding the explorer view > b) after some seconds (seems there is a timeout) a login dialog comes up saying I need to sign in (no clear info that auth failed or token missing etc.). > cancel the dialog since I'm trying to figure out what happened. > c) Now the explorer just shows "You must obtain API token by visiting ..." as child and I cannot see straightforward way to log in again. > Turns out Refresh does trigger login again. > meanwhile command line 'oc' seem to be fine at logging in with token older than 24 hrs...can't verify that though, but in any case: > a) do a user really need to re-login every 24 hours ? > b) the error handling/dialogs shown are not very informative -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21652?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21652: -------------------------------- Fix Version/s: (was: 4.3.1.CR1) > We should make OS 3 application status more visible for users > ------------------------------------------------------------- > > Key: JBIDE-21652 > URL: https://issues.jboss.org/browse/JBIDE-21652 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Fix For: 4.4.0.Alpha1 > > > Currently it can be confusing for users when an application is not available because it's building. > We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters). > For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible. > OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016