October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Labels: deploy_latest scaling_pods_wizard (was: ) > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Priority: Critical > Labels: deploy_latest, scaling_pods_wizard > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22362 at 10/24/16 2:51 PM: -------------------------------------------------------------------- [~ibuziuk] I'm very sure that the weirdness is related to the following issue: JBIDE-23412 I think that when restarting/debugging a new replication controller is created and the server adapter is still referencing the old one (or something very close to this). was (Author: adietish): [~ibuziuk] I'm very sure that the weirdness is related to the following issue: JBIDE-23412 > 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: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Priority: Critical (was: Major) > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Priority: Critical > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22362: ------------------------------------------ [~ibuziuk] I'm very sure that the weirdness is related to the following issue: JBIDE-23412 > 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: javascript, openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Ilya Buziuk > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM3 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Attachment: scale-to-shows-old-rc.ogv > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Steps to Reproduce: The following steps can be seen in the following screencast: [^scale-to-shows-old-rc.ogv] # ASSERT: have an app running (ex. nodejs-example) # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" # ASSERT: in Properties view: "Deployments" now shows 2 Deployments # ASSERT: in OpenShift Explorer you now see 2 children/pods # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service Result: The current number of pods is shown as 0. !replicas-0.png! But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: !rc2-replicas-1.png! The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. !rc-1-replicas-0.png! was: # ASSERT: have an app running (ex. nodejs-example) # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" # ASSERT: in Properties view: "Deployments" now shows 2 Deployments # ASSERT: in OpenShift Explorer you now see 2 children/pods # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service Result: The current number of pods is shown as 0. !replicas-0.png! But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: !rc-2-replicas-1.png! The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. !rc-1-replicas-0.png! > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23412: ------------------------------------- Attachment: rc2-replicas-1.png rc-1-replicas-0.png replicas-0.png > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23412: ---------------------------------------- Summary: Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" Key: JBIDE-23412 URL: https://issues.jboss.org/browse/JBIDE-23412 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Andre Dietisheim -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4132) Could not load nodeJSInstall: node-v0.10.22-linux-x86_64

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4132?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4132: ---------------------------------- Hopefully this will fix things: https://github.com/jbdevstudio/jbdevstudio-product/commit/badab6ed6c09ab7... Rebuilding: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/ >=284 > Could not load nodeJSInstall: node-v0.10.22-linux-x86_64 > -------------------------------------------------------- > > Key: JBDS-4132 > URL: https://issues.jboss.org/browse/JBDS-4132 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Fix For: 10.2.0.AM3 > > > Snippet from the log attached to JBDS-4131: > {code}!ENTRY tern.eclipse.ide.server.nodejs.core 4 0 2016-10-21 14:34:24.958 > !MESSAGE Could not load nodeJSInstall: node-v0.10.22-linux-x86_64 > !STACK 0 > java.io.FileNotFoundException: /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64_1.1.0.201511082254/node-v0.10.22-linux-x86_64/LICENSE (No such file or directory) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at tern.utils.ZipUtils.extract(ZipUtils.java:83) > at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstall.<init>(NodejsInstall.java:56) > at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.addNodejsInstalls(NodejsInstallManager.java:132) > at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.loadNodejsInstalls(NodejsInstallManager.java:117) > at tern.eclipse.ide.server.nodejs.internal.core.NodejsInstallManager.getNodejsInstalls(NodejsInstallManager.java:69) > at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.useBundledNodeJsInstall(TernNodejsCorePreferenceConstants.java:91) > at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDirectAccess(TernNodejsCorePreferenceConstants.java:70) > at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceConstants.initializeDefaultValues(TernNodejsCorePreferenceConstants.java:45) > at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferenceInitializer.initializeDefaultPreferences(TernNodejsCorePreferenceInitializer.java:24) > at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper$1.run(PreferenceServiceRegistryHelper.java:298) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.runInitializer(PreferenceServiceRegistryHelper.java:301) > at org.eclipse.core.internal.preferences.PreferenceServiceRegistryHelper.applyRuntimeDefaults(PreferenceServiceRegistryHelper.java:131) > at org.eclipse.core.internal.preferences.PreferencesService.applyRuntimeDefaults(PreferencesService.java:370) > at org.eclipse.core.internal.preferences.DefaultPreferences.applyRuntimeDefaults(DefaultPreferences.java:222) > at org.eclipse.core.internal.preferences.DefaultPreferences.load(DefaultPreferences.java:276) > at org.eclipse.core.internal.preferences.EclipsePreferences.create(EclipsePreferences.java:370) > at org.eclipse.core.internal.preferences.EclipsePreferences.internalNode(EclipsePreferences.java:623) > at org.eclipse.core.internal.preferences.DefaultPreferences.node(DefaultPreferences.java:147) > at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getDefaultPreferences(PreferenceForwarder.java:134) > at org.eclipse.core.internal.preferences.legacy.PreferenceForwarder.getString(PreferenceForwarder.java:663) > at tern.eclipse.ide.core.preferences.PreferencesSupport.getWorkspacePreferencesValue(PreferencesSupport.java:115) > at tern.eclipse.ide.server.nodejs.internal.core.preferences.TernNodejsCorePreferencesSupport.isNodejsRemoteAccess(TernNodejsCorePreferencesSupport.java:147) > at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.isRemoteAccess(TernNodejsServerFactory.java:67) > at tern.eclipse.ide.server.nodejs.internal.core.TernNodejsServerFactory.create(TernNodejsServerFactory.java:35) > at tern.eclipse.ide.internal.core.TernServerType.createServer(TernServerType.java:90) > at tern.eclipse.ide.internal.core.resources.IDETernProject.getTernServer(IDETernProject.java:161) > at tern.resources.TernFileSynchronizer.ensureSynchronized(TernFileSynchronizer.java:160) > at tern.eclipse.ide.internal.ui.EditorActivationTracker$2.run(EditorActivationTracker.java:85) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > !ENTRY tern.eclipse.ide.core 4 0 2016-10-21 14:34:27.182 > !MESSAGE java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory > !STACK 0 > tern.TernException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory > at tern.eclipse.ide.internal.core.resources.IDETernFileUploader$1.onError(IDETernFileUploader.java:133) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:131) > at tern.eclipse.ide.internal.core.resources.IDETernFileUploader.run(IDETernFileUploader.java:124) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: tern.server.nodejs.process.NodejsProcessException: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory > at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:245) > at tern.server.nodejs.process.AbstractNodejsProcess.start(AbstractNodejsProcess.java:144) > at tern.server.nodejs.NodejsTernServer.getBaseURL(NodejsTernServer.java:202) > at tern.server.nodejs.NodejsTernServer.makeRequest(NodejsTernServer.java:139) > at tern.server.nodejs.NodejsTernServer.request(NodejsTernServer.java:127) > ... 2 more > Caused by: java.io.IOException: Cannot run program "node" (in directory "/home/lvalach/rpm-workspace/StaticWebProject"): error=2, No such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) > at tern.server.nodejs.process.internal.NodejsProcess.start(NodejsProcess.java:232) > ... 6 more > Caused by: java.io.IOException: error=2, No such file or directory > at java.lang.UNIXProcess.forkAndExec(Native Method) > at java.lang.UNIXProcess.<init>(UNIXProcess.java:247) > at java.lang.ProcessImpl.start(ProcessImpl.java:134) > at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) > ... 7 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4133: ---------------------------------- Hopefully this will fix things: https://github.com/jbdevstudio/jbdevstudio-product/commit/badab6ed6c09ab7... Rebuilding: http://wonka.mw.lab.eng.bos.redhat.com/jenkins/job/devstudio.rpm_master/ >=284 > Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+ > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-4133 > URL: https://issues.jboss.org/browse/JBDS-4133 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Fix For: 10.2.0.AM3 > > > Snippet from log attached to JBDS-4131: > {code} > !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519 > !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629 > !STACK 0 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code} > And > {code} > !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719 > !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher. > {code} > then 100s of errors like this: > {code} > !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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