March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3661: -------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/1001 > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config > ------------------------------------------------------------------ > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Labels: havoc > Fix For: 9.1.0.CR1 > > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21815: ----------------------------------------------- I have tested the wizard with mock implementation of IDockerConnection, IDockerImageInfo, IDockerContainerConfig, and could not reproduce the problem - content of all viewers on all pages of the wizard is refreshed. [~xcoulon], could you please check if some exceptions are logged that might prevent updating image info? Could you also check if all the data on second and and next pages is for the previous image selection, or at least some of it is refreshed? > Image metadata not refreshed after name change > ---------------------------------------------- > > Key: JBIDE-21815 > URL: https://issues.jboss.org/browse/JBIDE-21815 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > > Steps to reproduce: > - open the *Deploy Docker Image* wizard > - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}} > - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again. > - ASSERT: the metadata should have been updated > - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21731) Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21731?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21731: --------------------------------------- [~adietish] the capability I suggest will only load tags and provides a more direct way to pull image data. If you do not need the other functionality provided by DeploymentResourceMapper I would skip it all together. No watch is available for imagestreamtags so DeploymentResourceMapper will never provide updates for that particular kind. > Server Adapter: Error shown when image is not created/pushed yet, sould be more user friendly > --------------------------------------------------------------------------------------------- > > Key: JBIDE-21731 > URL: https://issues.jboss.org/browse/JBIDE-21731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > Attachments: cannot_get_image.png > > > When I create a new OS3 application and then I want to create a new server adapter, an image for this application has to be built and pushed to OpenShift's local image registry. If build is still running, what is often happening on internal OSE instance (it takes minutes - pushing of images), then there is an error message that loading of image failed. User without solid overview of OS3 background would not be able to figure out why it is happening, because even Image stream is shown, but the image is not there yet. > Full error log: > {code} > com.openshift.restclient.OpenShiftException: Could not get resource django-example:latest in namespace image: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "imageStreamTag \"django-example:latest\" not found", > "reason": "NotFound", > "details": { > "name": "django-example:latest", > "kind": "imageStreamTag" > }, > "code": 404 > } > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:481) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:306) > at org.jboss.tools.openshift.core.connection.Connection.getResource(Connection.java:378) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$5(DeploymentResourceMapper.java:106) > at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getImageStreamTagsFor(DeploymentResourceMapper.java:107) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.lambda$2(DeploymentResourceMapper.java:87) > at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321) > at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) > at java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1540) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.models.DeploymentResourceMapper.getAllImageStreamTags(DeploymentResourceMapper.java:85) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.createImageStreamsMap(ServerSettingsViewModel.java:334) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel$ProjectImageStreamTags.<init>(ServerSettingsViewModel.java:327) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.lambda$1(ServerSettingsViewModel.java:279) > at java.util.stream.Collectors.lambda$toMap$213(Collectors.java:1321) > at java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169) > at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374) > at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481) > at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) > at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.createImageStreamTagsMap(ServerSettingsViewModel.java:277) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:261) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsViewModel.loadResources(ServerSettingsViewModel.java:255) > at org.jboss.tools.openshift.internal.ui.server.ServerSettingsWizardFragment$15.run(ServerSettingsWizardFragment.java:695) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: com.openshift.internal.restclient.http.NotFoundException: { > "kind": "Status", > "apiVersion": "v1", > "metadata": {}, > "status": "Failure", > "message": "imageStreamTag \"django-example:latest\" not found", > "reason": "NotFound", > "details": { > "name": "django-example:latest", > "kind": "imageStreamTag" > }, > "code": 404 > } > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:230) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:165) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:141) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:103) > at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:302) > ... 36 more > Caused by: java.io.FileNotFoundException: https://console.engint.openshift.com/oapi/v1/namespaces/image/imagestream... > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1836) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1441) > at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > at com.openshift.internal.restclient.http.UrlConnectionHttpClient.request(UrlConnectionHttpClient.java:161) > ... 39 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-295) utilize the tycho testing support for test bundles on JBTIS

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-295?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-295: ------------------------------------------- Whent SwitchYard (as an example) uses the JBTIS TP to run its unit test against it it will *not* necessarily load all parts of JBDS - it will only load/start the bundles your test and its dependencies declare. With Michael's approach here you can run tests inside a specific version of developer studio (i.e. devstudio 9.1 beta) instead of just the dependency set. Thus I think it would help catch other kind of errors - but that would probably need new tests that are more integration level tests (i.e. does SwitchYard start in JBDS without any errors as opposed to testing SY unit level features works). > utilize the tycho testing support for test bundles on JBTIS > ----------------------------------------------------------- > > Key: JBTIS-295 > URL: https://issues.jboss.org/browse/JBTIS-295 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: testing > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > > Talking with [~rcernich] he was interested in doing testing of already packaged bundles on a packaged eclipse. > [~mickael_istria] did this feature for tycho 0.19 documented at http://wiki.eclipse.org/Tycho/Release_Notes/0.19#Test_Execution > [~rcernich] would this cover you intended use case ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21807) Cannot publish changes to OpenShift 2 application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21807?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21807: ------------------------------------------ [~mlabuda] I installed jboss-devstudio-9.1.0.CR1-v20160303-1242-B378 and I still cant reproduce this. I believe that this is an issue in your installation. > Cannot publish changes to OpenShift 2 application > ------------------------------------------------- > > Key: JBIDE-21807 > URL: https://issues.jboss.org/browse/JBIDE-21807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v2, server_adapter > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Cannot publish changes via OpenShift 2 server adapter to OpenShift 2 application. There is following stack in error log: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/eclipse/egit/core/AdaptableFileTreeIterator) > 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:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > 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:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > 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:498) > 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) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > Caused by: java.lang.NoClassDefFoundError: org/eclipse/egit/core/AdaptableFileTreeIterator > at org.jboss.tools.openshift.express.internal.ui.server.CommitUI.commit(CommitUI.java:194) > at org.jboss.tools.openshift.express.internal.ui.server.EGitUI$1.run(EGitUI.java:39) > 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) > ... 24 more > Caused by: java.lang.ClassNotFoundException: org.eclipse.egit.core.AdaptableFileTreeIterator cannot be found by org.jboss.tools.openshift.express.ui_3.1.0.CR1-v20160302-0336-B205 > at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352) > at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344) > at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 30 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3661: ------------------------------------ Assignee: Rob Stryker (was: Max Rydahl Andersen) > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config > ------------------------------------------------------------------ > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Labels: havoc > Fix For: 9.1.0.CR1 > > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3661: --------------------------------- Fix Version/s: 9.1.0.CR1 > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config > ------------------------------------------------------------------ > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Rob Stryker > Labels: havoc > Fix For: 9.1.0.CR1 > > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by Denis Golovin (JIRA)

Denis Golovin created JBDS-3661: ----------------------------------- Summary: Remove VAGRANT_DETECTED_OS from env variables in CDK launch config Key: JBDS-3661 URL: https://issues.jboss.org/browse/JBDS-3661 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: cdk, server Affects Versions: 9.1.0.Beta2 Reporter: Denis Golovin Assignee: Max Rydahl Andersen With mingw based ssh/rsync this env varibale is not required. It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3661: -------------------------------- Labels: havoc (was: ) > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config > ------------------------------------------------------------------ > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Labels: havoc > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3661) Remove VAGRANT_DETECTED_OS from env variables in CDK launch config

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3661?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3661: ----------------------------- > Remove VAGRANT_DETECTED_OS from env variables in CDK launch config > ------------------------------------------------------------------ > > Key: JBDS-3661 > URL: https://issues.jboss.org/browse/JBDS-3661 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, server > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Max Rydahl Andersen > Labels: havoc > > With mingw based ssh/rsync this env varibale is not required. > It is also set in windows user env variables, so there is no reason to duplicate that anyway. -- 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 March 2016