[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22626:
-------------------------------------
Summary: 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
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
[JBoss JIRA] (JBIDE-22515) Deploying/Pushing an updated docker image causes an error because of conflicting resources
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22515?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-22515.
---------------------------------
Verified in devstudio 10.0 GA respin-b.
> Deploying/Pushing an updated docker image causes an error because of conflicting resources
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-22515
> URL: https://issues.jboss.org/browse/JBIDE-22515
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> After a docker image has been successfully deployed to OpenShift, if the image has been updated to a new version in the daemon, performing a second Deploy to OpenShift command will effectively update the image but an error will popup about resources already existing.
> I believe that, when we're about to create the openshift resources, we should
> - detect if there's already a matching deployment config for the same project/resource name)
> - if the deployment config links to an imagestream matching the docker image being deployed, then it's an update, then bail without creating any resources, else resource conflict checks should happen.
> Ideally, this should probably happen at the wizard level, so we don't need to show the resource pages and go straight to finish, but that can be implemented later
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3953:
--------------------------------------
Thanks everyone!
> JBoss Studio Developer crash at startup on Fedora 24
> ----------------------------------------------------
>
> Key: JBDS-3953
> URL: https://issues.jboss.org/browse/JBDS-3953
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 9.1.0.GA
> Environment: Fedora 24
> openjdk full version "1.8.0_92-b14"
> Reporter: Donato Marrazzo
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.0.0.GA
>
> Attachments: hs_err_pid12689.log, hs_err_pid3836.log.zip, Selection_003.png
>
>
> After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash.
> Despite the console message, no core dump is generated.
> This is the cmd line output:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml]
> openjdk version "1.8.0_92"
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode)
> 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository
> 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml]
> 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml]
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700
> #
> # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14)
> # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e
> #
> # Core dump written. Default location: /home/donato/core or core.12689
> #
> # An error report file with more information is saved as:
> # /home/donato/hs_err_pid12689.log
> #
> # If you would like to submit a bug report, please visit:
> # http://bugreport.java.com/bugreport/crash.jsp
> # The crash happened outside the Java Virtual Machine in native code.
> # See problematic frame for where to report the bug.
> #
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22362:
---------------------------------------
That's true, that debugging is enabled when DEV_MODE is true. But from tooling point of view, having just exposed port is not all work done. By restarting server adapter in debug mode we still have to start port forwarding on a nodejs application and attach nodejs debugger to it with specific port. So that's done in advance and it makes much more than just setting an environment variable (which enables nodemon on the pod(s)).
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Marián Labuda
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.1.S116
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22622) Opening the Web Console in the embedded browser (by default) results in error
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22622?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22622:
----------------------------------------
[~jeffmaury] but it works fine in your external browser, correct?
> Opening the Web Console in the embedded browser (by default) results in error
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22622
> URL: https://issues.jboss.org/browse/JBIDE-22622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.S116
> Reporter: Fred Bricon
> Priority: Critical
> Attachments: 2016-06-21 at 10-05-24.mp4
>
>
> The Web Console opens using whatever browser is set in Eclipse (internal by default). When using the default browser, after logging in, there's an error message stating "Server connection interrupted". This error occurs on OSX and Linux at least.
> I think the web console should be opened in the external browser in all cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22622) Opening the Web Console in the embedded browser (by default) results in error
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22622?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22622:
-----------------------------------
Sprint: devex #117 2016/07/06 - 07/26
> Opening the Web Console in the embedded browser (by default) results in error
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22622
> URL: https://issues.jboss.org/browse/JBIDE-22622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.S116
> Reporter: Fred Bricon
> Priority: Critical
> Attachments: 2016-06-21 at 10-05-24.mp4
>
>
> The Web Console opens using whatever browser is set in Eclipse (internal by default). When using the default browser, after logging in, there's an error message stating "Server connection interrupted". This error occurs on OSX and Linux at least.
> I think the web console should be opened in the external browser in all cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22622) Opening the Web Console in the embedded browser (by default) results in error
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22622?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22622:
-----------------------------------
Priority: Critical (was: Major)
> Opening the Web Console in the embedded browser (by default) results in error
> -----------------------------------------------------------------------------
>
> Key: JBIDE-22622
> URL: https://issues.jboss.org/browse/JBIDE-22622
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.S116
> Reporter: Fred Bricon
> Priority: Critical
> Attachments: 2016-06-21 at 10-05-24.mp4
>
>
> The Web Console opens using whatever browser is set in Eclipse (internal by default). When using the default browser, after logging in, there's an error message stating "Server connection interrupted". This error occurs on OSX and Linux at least.
> I think the web console should be opened in the external browser in all cases.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22038) Errors on startup with Java 9
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22038?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-22038.
-----------------------------------
Fix Version/s: 4.4.0.Final
Resolution: Done
I believe this is done. The current outstanding issue is tracked here: JBIDE-22417
> Errors on startup with Java 9
> -----------------------------
>
> Key: JBIDE-22038
> URL: https://issues.jboss.org/browse/JBIDE-22038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Martin Malina
> Labels: java9
> Fix For: 4.4.0.Final
>
>
> Starting fresh JBT/JBDS with Java 9 results in an error dialog popping up with these two errors:
> {noformat}An internal error occurred during: "Update project wizard list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38)
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1064)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:282)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:273)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> 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:356)
> ... 6 more{noformat}
> {noformat}An internal error occurred during: "Download quickstarts list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263)
> at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> 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:356)
> ... 7 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22417) Eclipse will not run with java9 - NoClassDefFoundError
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22417?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-22417:
----------------------------------
Labels: java9 (was: )
> Eclipse will not run with java9 - NoClassDefFoundError
> ------------------------------------------------------
>
> Key: JBIDE-22417
> URL: https://issues.jboss.org/browse/JBIDE-22417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.4.0.Alpha2
> Reporter: Martin Malina
> Assignee: Alexey Kazakov
> Priority: Critical
> Labels: java9
> Fix For: 4.4.x
>
>
> As of the latest build of Oracle JDK 9, Eclipse Neon M7 will not start.
> Java version:
> {code}
> $ java -version
> java version "9-ea"
> Java(TM) SE Runtime Environment (build 9-ea+118)
> Java HotSpot(TM) 64-Bit Server VM (build 9-ea+118, mixed mode)
> {code}
> Error log:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2016-05-19 11:14:42.241
> !MESSAGE Application error
> !STACK 1
> org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:626)
> 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 jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(java.base@9-ea/Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(java.base@9-ea/NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(java.base@9-ea/DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(java.base@9-ea/Method.java:531)
> 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)
> Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)
> ... 22 more
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 24 more
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-05-19 11:14:42.248
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.NoClassDefFoundError: javax/annotation/PreDestroy
> at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)
> at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:78)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:175)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)
> at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)
> at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)
> at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)
> at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)
> at org.eclipse.osgi.container.Module.doStop(Module.java:634)
> at org.eclipse.osgi.container.Module.stop(Module.java:498)
> at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191)
> at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165)
> at java.lang.Thread.run(java.base@9-ea/Thread.java:804)
> Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:394)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(java.base@9-ea/ClassLoader.java:419)
> ... 21 more
> {code}
> Upstream issue - targeted for Neon.1:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=493761
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months