[JBoss JIRA] (JBIDE-22898) FileNotFoundException below BatchBuilder$BatchResourceVisitor.visit (thrown in FileInputStream.open0)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22898?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-22898.
---------------------------------
I have added new auto action that reopens JIRA (via AERI report system) in case that exception will appear again in new version (1.8.0) of org.jboss.tools.batch.core. Closing this JIRA.
> FileNotFoundException below BatchBuilder$BatchResourceVisitor.visit (thrown in FileInputStream.open0)
> -----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22898
> URL: https://issues.jboss.org/browse/JBIDE-22898
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.1.Final
>
>
> The following problem was reported via the automated error reporting:
> Message: HIDDEN
> {noformat}
> java.io.FileNotFoundException: HIDDEN
> at java.io.FileInputStream.open0(FileInputStream.java:-2)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at org.eclipse.core.internal.filesystem.local.LocalFile.openInputStream(LocalFile.java:382)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:834)
> at org.eclipse.core.internal.resources.File.getContents(File.java:269)
> at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1190)
> at org.eclipse.jdt.internal.core.util.Util.getResourceContentsAsCharArray(Util.java:1164)
> at org.eclipse.jdt.internal.core.CompilationUnit.openBuffer(CompilationUnit.java:1160)
> at org.eclipse.jdt.internal.core.CompilationUnit.buildStructure(CompilationUnit.java:115)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:259)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:579)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:316)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:302)
> at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:257)
> at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:271)
> at org.eclipse.jdt.internal.core.CompilationUnit.getTypes(CompilationUnit.java:923)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder$BatchResourceVisitor.visit(BatchBuilder.java:415)
> at org.eclipse.core.internal.resources.Resource$2.visit(Resource.java:119)
> at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:83)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:87)
> at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:129)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:93)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:51)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:116)
> at org.eclipse.core.internal.resources.Resource.accept(Resource.java:104)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.fullBuild(BatchBuilder.java:178)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.build(BatchBuilder.java:150)
> at org.jboss.tools.batch.internal.core.impl.BatchBuilder.<init>(BatchBuilder.java:73)
> at org.jboss.tools.batch.internal.core.impl.BatchProject.build(BatchProject.java:341)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.load(AbstractKbProjectExtension.java:163)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolveStorage(AbstractKbProjectExtension.java:154)
> at org.jboss.tools.jst.web.kb.internal.AbstractKbProjectExtension.resolve(AbstractKbProjectExtension.java:148)
> at org.jboss.tools.batch.internal.core.impl.BatchProject$BatchBuildJob.runInWorkspace(BatchProject.java:120)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.filesystem | 1.5.0.v20150725-1910 | 1.6.0.v20160503-1608 |
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt.core | 3.11.0.v20150622-0644_BETA_JAVA9 | 3.12.0.v20160516-2131 |
> | org.eclipse.jface.text | 3.10.0.v20150603-1752 | 3.10.0.v20150603-1752 |
> | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.401.v201510130005 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.batch.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> Operating Systems:
> | Linux | 3.13.0 | 4.6.4.fc23 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/575a5668e4b06056d2...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23049) Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-23049:
-------------------------------------
Summary: Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
Key: JBIDE-23049
URL: https://issues.jboss.org/browse/JBIDE-23049
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.4.1.Final
Environment: Eclipse SDK
Version: Neon.1 (4.6.1)
Build id: M20160824-0059
JBoss Tools from update site:
http://download.jboss.org/jbosstools/neon/snapshots/updates/
org.jboss.tools.common.mylyn:
3.8.1.v20160607-2053
Reporter: Josef Kopriva
An error is shown in error log after installing JBoss Tools in Eclipse Neon.1 RC2:
{code:java}
Unexpected error while loading repository template extensions
Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'bugzilla'
{code}
Stacktrace:
{code:java}
An exception stack trace is not available.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23042) CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23042?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23042:
-------------------------------------
Forum Reference: https://github.com/projectatomic/vagrant-service-manager/issues/383
> CDK server adapter: Can't launch latest CDK 2.2 in Windows 10
> -------------------------------------------------------------
>
> Key: JBIDE-23042
> URL: https://issues.jboss.org/browse/JBIDE-23042
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: cdk
> Fix For: 4.4.1.Final
>
> Attachments: vagrant-output.txt
>
>
> When launching the latest CDK 2.2 candidate the following error occurrs:
> {code}
> [landrush] Using eth1 (172.28.128.3)
> [landrush] adding Landrush'es DNS server to network 'VirtualBox Host-Only Network #3' using DNS IP '172.28.128.3'' and search domain 'cdk'
> ==> default: The folowing SH comand responded with a non-zero exit status.
> ==> default: Vagrant asumes that this means the comand failed!
> ==> default: sudo rm /etc/docker/ca.pem & sudo systemctl restart docker
> ==> default: Stdout from the comand:
> ==> default: Stder from the comand:
> ==> default: rm: canot remove '/etc/docker/ca.pem': No such file or directory
> ==> default: Forcing shutdown of VM...
> ==> default: Destroying VM and associated drives...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> ==> default: Running cleanup tasks for 'shell' provisioner...
> C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/services/docker.rb:20:in `execute': undefined method `zero?' for #<Thread:0x24a7250 dead> (NoMethodError)
> from C:/Users/Administrator/.vagrant.d/gems/gems/vagrant-service-manager-1.4.0.dev/lib/vagrant-service-manager/service.rb:20:in `each'
> {code}
> The complete vagrant output is here: [^vagrant-output.txt]
> See the following mail that Rob sent to the mailing list: http://post-office.corp.redhat.com/archives/devtools-program/2016-August/...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23031:
------------------------------------------
[~rhopp] Can you please review/test this change?
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22914) OpenShift Deployment: Deploy latest does not work correctly
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22914?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22914:
-------------------------------------
Fix Version/s: 4.4.1.Final
> OpenShift Deployment: Deploy latest does not work correctly
> -----------------------------------------------------------
>
> Key: JBIDE-22914
> URL: https://issues.jboss.org/browse/JBIDE-22914
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.1.Final
>
>
> When I have an application where no replication controller is yet and I want to deploy latest, I get following error:
> {code}
> Unable to perform a deployment for config hello-openshift
> com.openshift.restclient.NotFoundException: replicationcontrollers "hello-openshift-0" not found
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:105)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:59)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:200)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:181)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:269)
> at com.openshift.internal.restclient.capability.resources.DeployCapability.deploy(DeployCapability.java:59)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:90)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1$1.visit(TriggerDeploymentHandler.java:1)
> at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:91)
> at org.jboss.tools.openshift.internal.ui.handler.TriggerDeploymentHandler$1.doRun(TriggerDeploymentHandler.java:85)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
> This is wrong, because it is trying to "deploy latest replication controller" instead of deploying latest deployment configuration (as it works e.g. from oc binary - deployment uses latest deployment configuration not replication controller which could be understood as instance of deployment configuration). Therefore if there is no replication controller and I click Deploy Latest in context menu of a service in OpenShift Explorer view or in context menu of a deployment configuration in properties view, I get the error.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23014:
-------------------------------------
Labels: connection connection_wizard openshift_v3 (was: )
> Allow connections to configure the cluster namespace from which to get clusterwide templates
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-23014
> URL: https://issues.jboss.org/browse/JBIDE-23014
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Labels: connection, connection_wizard, openshift_v3
> Fix For: 4.4.x
>
>
> There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22912) Deploy Docker Wizard: Inappropriate project combo size
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22912?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22912:
-------------------------------------
Labels: deploy_docker_wizard openshift_v3 (was: )
> Deploy Docker Wizard: Inappropriate project combo size
> ------------------------------------------------------
>
> Key: JBIDE-22912
> URL: https://issues.jboss.org/browse/JBIDE-22912
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Priority: Minor
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.x
>
> Attachments: project_combo.png
>
>
> In Deploy Docker Image wizard opened from context menu of a docker image is project combo stretched to left size and it does not look good.
> !project_combo.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months