[JBoss JIRA] (JBIDE-22603) Sometimes multiple OpenShift watch managers are periodically created and finished
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22603?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22603:
-------------------------------
Attachment: watchers.log
> Sometimes multiple OpenShift watch managers are periodically created and finished
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-22603
> URL: https://issues.jboss.org/browse/JBIDE-22603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Final
> Reporter: Marián Labuda
> Assignee: Jeff MAURY
> Priority: Blocker
> Labels: explorer, openshift_v3
> Fix For: 4.4.1.AM3
>
> Attachments: openshift_watchers.ogv, watchers.log, watchers.png
>
>
> Sometimes when I am working with OpenShift toolings, there are created multiple OpenShift Watch Managers which are getting finished, disappearing from Progress view and another new ones are created and this repeats nonstop. Sometimes there are 2-3 running, sometimes even more. I am working with openshift-dev user, where is visible default project (still, until patch in upstream get effect) and my own project with application created from eap 6.4 basic s2i template.
> !watchers.png!
> It would not be a problem but I have a hunch it is the problem breaking automatic update of OpenShift explorer view to reflect current state and existence of resources on OpenShift server. E.g. under a service there is build table visible all the time and no application pod is shown, even build is finished and there is an application pod running on OpenShift. Another example when it is not working is when I am scaling application up/down - it does not reflect real amount of application pods.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22274) Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
by Jeff Johnston (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22274?page=com.atlassian.jira.plugi... ]
Jeff Johnston updated JBIDE-22274:
----------------------------------
Sprint: devex #116 June 2016, devex #118 July 2016 (was: devex #116 June 2016)
> Show In->System Explorer on docker volume is not working when the volume is just a file (not a directory)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22274
> URL: https://issues.jboss.org/browse/JBIDE-22274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: JBDS 10.0.0.Alpha1-v20160428-0509-B5247
> Reporter: Radim Hopp
> Assignee: Jeff Johnston
> Fix For: 4.4.1.AM2
>
>
> Start docker container with -v parameter pointing to some file. For example: "docker run -d -p 5000:5000 -v /home/rhopp/temp/config.yml_new:/etc/docker/registry/config.yml --name registry1 registry:2"
> Go to Docker Explorer, expand running container->right click on the only volume in there->Show In->System Explorer-> Error is logged:
> {noformat:title=Failed to open in Web Browser}
> java.io.IOException: Cannot run program "/bin/sh" (in directory "/home/rhopp/temp/config.yml_new"): error=20, Not a directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
> at java.lang.Runtime.exec(Runtime.java:620)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.getLaunchProcess(ShowInSystemExplorerCommandHandler.java:99)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler.access$0(ShowInSystemExplorerCommandHandler.java:96)
> at org.eclipse.linuxtools.internal.docker.ui.commands.ShowInSystemExplorerCommandHandler$1.run(ShowInSystemExplorerCommandHandler.java:65)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.io.IOException: error=20, Not a directory
> at java.lang.UNIXProcess.forkAndExec(Native Method)
> at java.lang.UNIXProcess.<init>(UNIXProcess.java:248)
> at java.lang.ProcessImpl.start(ProcessImpl.java:134)
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-654:
----------------------------------
Progress bar issue is https://issues.jboss.org/browse/JBDS-3985 - will be fixed soon.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: Capture.JPG, inst1.png, inst1.png, inst1a.png, inst2.png, inst3.png, inst4.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. i.e. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22807) Could not install bundle. A bundle is already installed with the name xxx
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22807?page=com.atlassian.jira.plugi... ]
Rastislav Wagner reassigned JBIDE-22807:
----------------------------------------
Assignee: Rastislav Wagner
Resolution: Done
PR merged
> Could not install bundle. A bundle is already installed with the name xxx
> -------------------------------------------------------------------------
>
> Key: JBIDE-22807
> URL: https://issues.jboss.org/browse/JBIDE-22807
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: qa
> Environment: Fedora 24, x86_64
> devstudio:
> Version: 10.0.1.AM2
> Build id: AM2-v20160720-1632-B5674
> OpenJDK Runtime Environment (build 1.8.0_92-b14)
> Reporter: Ondrej Dockal
> Assignee: Rastislav Wagner
> Priority: Critical
> Fix For: 4.4.1.AM3
>
>
> Error log contains errors for each plugin installed in devstudio where tests are run on existing instance of devstudio via mvn command (test is run with parameter test.installBase=path/to/devstudio)
> Could not install bundle plugins/org.eclipse.mylyn.commons.net_3.20.0.v20160421-1819.jar A bundle is already installed with the name "org.eclipse.mylyn.c... (Open log entry details for full message).
> This imply also for probably all jobs that install devstudio on machines through groovy script and run integration tests. Unless error log is checked in test, this does not mind...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22735) CDK Server adapter is not available in Quick Access bar when typing "cdk"
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22735?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22735.
---------------------------------
Both cdk and cde can be used to access the command in quick access now. Verified in devstudio-10.1.0.AM3-v20160802-1710-B5682-installer-standalone.jar .
But one question for [~rob.stryker], is there a way to actually show the full command name? Because in my case the table is too narrow so I can't even see the full name - I only see "Launch Container Development Environ" and that's it.
> CDK Server adapter is not available in Quick Access bar when typing "cdk"
> -------------------------------------------------------------------------
>
> Key: JBIDE-22735
> URL: https://issues.jboss.org/browse/JBIDE-22735
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.1.AM3
>
>
> I guess this is a side effect of renaming "CDK Server Adapter" to "Container Development Environment".
> We need to investigate if the only way to make the adapter available for "cdk" is to have "cdk" mentioned in the server type name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months