[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23030:
------------------------------------------
merged PR into master.
> Scaling a service changes the wrong deployment
> ----------------------------------------------
>
> Key: JBIDE-23030
> URL: https://issues.jboss.org/browse/JBIDE-23030
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Priority: Critical
> Fix For: 4.4.2.AM3
>
> Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv
>
>
> In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift.
> The workaround is to open the properties view and issue a scale command on a deployment directly.
> However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP
> (copied from JBIDE-23412)
> 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!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4146:
--------------------------------------
I don't see this problem now. Not sure if something was actually fixed but AERI seems to work for me now.
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !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/1477679545041-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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4146:
--------------------------------------
Nick, can you verify this issue on the latest build?
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !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/1477679545041-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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov edited comment on JBDS-4146 at 11/2/16 6:29 PM:
---------------------------------------------------------------
[~nickboldt], can you verify this issue on the latest build?
was (Author: akazakov):
Nick, can you verify this issue on the latest build?
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !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/1477679545041-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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4153:
----------------------------------
Try running the installer with tracing enabled, eg.,
java -DTRACE=true -jar devstudio-10.2.0.AM2-v20161014-1657-B6205-installer-standalone.jar
Then attach any useful information that leads up to the cryptic error you're seeing.
You could also try installing to c:/devstudio (note the slash direction) or /devstudio - that might help?
> Cannot install Fuse Runtime on Windows using the installer
> ----------------------------------------------------------
>
> Key: JBDS-4153
> URL: https://issues.jboss.org/browse/JBDS-4153
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 10.x
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png
>
>
> On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails.
> i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0....
> !screenshot-1.png|thumbnail!
> !screenshot-2.png|thumbnail!
> !screenshot-3.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (ERT-439) Add remote mount support to ContainerLauncher [EBZ#506312]
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/ERT-439?page=com.atlassian.jira.plugin.sy... ]
Jeff Johnston updated ERT-439:
------------------------------
Sprint: devex #122 October 2016
> Add remote mount support to ContainerLauncher [EBZ#506312]
> ----------------------------------------------------------
>
> Key: ERT-439
> URL: https://issues.jboss.org/browse/ERT-439
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Linux Tools
> Reporter: Friendly Jira Robot
> Assignee: Jeff Johnston
> Labels: 5.2.0, Docker, bzira
> Fix For: Neon.2 (4.6)
>
>
> The ContainerLauncher class in Docker uses a HostConfig binds setting to mount specified mount points in the Container. This does not work when the daemon is remote. What needs to be done is to determine the daemon is remote and then create a mount point that we copy host files into before starting the container.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4149) JavaEE Web Project > Run As > Maven not working - constraint violation: javax.servlet-api 3.1.0 and javax.servlet 3.1.0.v201410161800
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4149?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4149:
----------------------------------
Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devs... >=566
> JavaEE Web Project > Run As > Maven not working - constraint violation: javax.servlet-api 3.1.0 and javax.servlet 3.1.0.v201410161800
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4149
> URL: https://issues.jboss.org/browse/JBDS-4149
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: ClassNotFoundEx_20161102_095940.png, eclipse.log, eclipse_10.2-0.20161101.1258.log, javax.servlet.310rpm_vs_orbit.png, rh-eclipse46-devstudio-snapshots-10_2.repo, rh-eclipse46.repo
>
>
> I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message:
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 10 more
> {code}
> Standalone maven installation works fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4146:
-----------------------------
Summary: Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException (was: Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+)
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !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/1477679545041-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}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4154) JavaEE Web Project > Run As > Maven not working
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4154?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4154:
----------------------------------
With rpm version 10.2 0.20161102.1838.el7 installed, I was able to:
1. install devstudio
2. git clone git@github.com:eclipse/thym.git
3. import all the projects from that repo
4. edit those projects, including classpath resolution & tweaks to MANIFEST.MF files
5. automatically compile them in Eclipse (background building)
But as noted, the workaround above is needed to support Run As > Maven build because of the slf4j error.
> JavaEE Web Project > Run As > Maven not working
> -----------------------------------------------
>
> Key: JBDS-4154
> URL: https://issues.jboss.org/browse/JBDS-4154
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7 64bit
> Reporter: Lukáš Valach
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> I am not able to use embedded Maven. When I try to run Maven clean (or whatever else) I get following error message in Console (nothing in Error log):
> {code}
> Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/Logger
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
> at java.lang.Class.getMethod0(Class.java:3018)
> at java.lang.Class.getMethod(Class.java:1784)
> at org.codehaus.plexus.classworlds.launcher.Launcher.getEnhancedMainMethod(Launcher.java:172)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:268)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassNotFoundException: org.slf4j.Logger
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
> ... 10 more
> {code}
> Standalone maven installation works fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months