August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22727: ------------------------------------- Story Points: 4 (was: 1) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.Final > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22994) Remove old Help->Report Problem dialog

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22994?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22994: ------------------------------------- Story Points: 4 > Remove old Help->Report Problem dialog > -------------------------------------- > > Key: JBIDE-22994 > URL: https://issues.jboss.org/browse/JBIDE-22994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, common/jst/core > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > Should we deprecate delete old Report Problem dialog with aeri enabled? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Story Points: 12 > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.1.Final > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23001: ------------------------------------- Sprint: devex #119 August 2016 > Application Wizard: NPE when opening OS 2 wizard from central or shell menu > --------------------------------------------------------------------------- > > Key: JBIDE-23001 > URL: https://issues.jboss.org/browse/JBIDE-23001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: application_wizard, openshift_v2, regression > Fix For: 4.4.1.Final > > > When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central. > stack trace of NPE: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23001: ------------------------------------- Story Points: 1 > Application Wizard: NPE when opening OS 2 wizard from central or shell menu > --------------------------------------------------------------------------- > > Key: JBIDE-23001 > URL: https://issues.jboss.org/browse/JBIDE-23001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: application_wizard, openshift_v2, regression > Fix For: 4.4.1.Final > > > When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central. > stack trace of NPE: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > 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:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > 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:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22994) Remove old Help->Report Problem dialog

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22994?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22994: ------------------------------------- Sprint: devex #119 August 2016 > Remove old Help->Report Problem dialog > -------------------------------------- > > Key: JBIDE-22994 > URL: https://issues.jboss.org/browse/JBIDE-22994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, common/jst/core > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > Should we deprecate delete old Report Problem dialog with aeri enabled? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23005: ------------------------------------------ JBIDE-22677 looks very closely matching this. We only have a single thread entry in the dump for JBIDE-22677 though. [~fbricon] can you confirm/refute? > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Final > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22853) Missing connection error shows sometimes on existing connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22853?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22853. --------------------------------- > Missing connection error shows sometimes on existing connection > --------------------------------------------------------------- > > Key: JBIDE-22853 > URL: https://issues.jboss.org/browse/JBIDE-22853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: connection, openshift_v3 > Fix For: 4.4.1.AM3 > > > Sometimes when I am working with console.engint.openshift.com instance where I use OAuth authentication, I get following error in error log with no stack trace when trying to create a project or application on a connection > {code} > Could not create project, missing connection. > {code} > Then when I open Edit Connection wizard via context menu of the connection, there is an error in header of the wizard "Connection for the server with this token already exists." > Not sure what precisely it is causing and how to reproduce it with success rate 100 %. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23009) Cannot connect to cdk docker in Docker Explorer

by Martin Malina (JIRA)

Martin Malina created JBIDE-23009: ------------------------------------- Summary: Cannot connect to cdk docker in Docker Explorer Key: JBIDE-23009 URL: https://issues.jboss.org/browse/JBIDE-23009 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker Affects Versions: 4.4.1.AM3 Reporter: Martin Malina Priority: Blocker When I start CDK 2.2, docker connection is correctly created, but it cannot connect. There is no error message anywhere. If I try to create a connection manually, using details from "vagrant service-manager env", the ping fails and it doesn't work either. Connection from CLI, on the other hand, to this docker daemon works fine - when I run the export commands: {code} export DOCKER_HOST=tcp://172.28.128.3:2376 export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc1/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.22 {code} and then try for example "docker ps" or "docker run hello-world". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23005) Server Adapter: Stuck on creating/publishing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23005?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23005: ------------------------------------- Summary: Server Adapter: Stuck on creating/publishing (was: Server Adapter: Stucked on creating/publishin OpenShift 3 server adapter) > Server Adapter: Stuck on creating/publishing > -------------------------------------------- > > Key: JBIDE-23005 > URL: https://issues.jboss.org/browse/JBIDE-23005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.Final > > Attachments: stucked_server_adapter > > > When I am trying to create a new OpenShift 3 server adapter, many times creation does not work. Server get stucked at publishing and there is a hanging job Check module status for server eap-app at OpenShift... I am using CDK OpenShift and build an application on eap 6.4 template with kitchensink context_dir. Connection is not established. While this is happening (job is hanging) there is no error in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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