July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22686) Can't push image to docker registry

by Dmitry Bocharov (JIRA)

Dmitry Bocharov created JBIDE-22686: --------------------------------------- Summary: Can't push image to docker registry Key: JBIDE-22686 URL: https://issues.jboss.org/browse/JBIDE-22686 Project: Tools (JBoss Tools) Issue Type: Bug Components: docker, openshift Affects Versions: 4.4.0.Final Environment: Fedora 23 Reporter: Dmitry Bocharov Attachments: DeployDockerImageToOS.webm The screencast of the last steps is attached. Properties and settings of the cdk haven't been changed. Everything is dowloaded and installed in a usual way. Possibly something is with the dns - maybe it wasn't configured correctly while cdk installation. Because we to push to the valid url, while OS connection only an IP in its settings. _exception:_ org.eclipse.linuxtools.docker.core.DockerException: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1047) at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:67) 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: com.spotify.docker.client.DockerException: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:42) at com.spotify.docker.client.ProgressStream.tail(ProgressStream.java:74) at com.spotify.docker.client.DefaultDockerClient.push(DefaultDockerClient.java:821) at org.eclipse.linuxtools.internal.docker.core.DockerConnection.pushImage(DockerConnection.java:1043) ... 3 more Caused by: org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/sample-project/aloha: unable to ping registry endpoint https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v0/ v2 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v2/: dial tcp 10.1.2.2:443: connection refused v1 ping attempt failed with error: Get https://hub.openshift.rhel-cdk.10.1.2.2.xip.io/v1/_ping: dial tcp 10.1.2.2:443: connection refused at org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler.processMessage(ImagePushProgressHandler.java:49) at org.eclipse.linuxtools.internal.docker.core.DockerProgressHandler.progress(DockerProgressHandler.java:40) ... 6 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Nick Boldt (JIRA)

Nick Boldt created JBDS-3960: -------------------------------- Summary: rename platform installer artifacts to start with "devsuite" instead of "development-suite" Key: JBDS-3960 URL: https://issues.jboss.org/browse/JBDS-3960 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.0.0.GA Reporter: Nick Boldt Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22605: --------------------------------------- And... I just tried this on Windows 10 and I can reproduce it all the same. Maybe it's something specific to my host? I tried again now on OS X with a fake remote server - using my own hostname as the remote server and connecting to it via ssh. This time it worked. I will email you access info. > Remote server with fs operations sometimes cannot be stopped > ------------------------------------------------------------ > > Key: JBIDE-22605 > URL: https://issues.jboss.org/browse/JBIDE-22605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work. > In one instance of Eclipse, stopping such server didn't work. > But then I tried in devstudio and it worked, so I assumed it was some glitch. > But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA. > From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine. > One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup: > {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code} > (Let me know if you want an additional JIRA for that.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22605: --------------------------------------- [~rob.stryker], I tried it again now. I started with a new workspace in devstudio 10. I followed the steps from Steps To Reproduce exactly. With the exception that I created the remote server without a runtime. So when I wanted to create the html5 project from central, I had to create an eap 7 local server first. And I could reproduce the problem with stopping of the server. I think I will need to test on another system to see if this is just me. For the problem with the missing marker, I don't have a clear way to reproduce this right now. > Remote server with fs operations sometimes cannot be stopped > ------------------------------------------------------------ > > Key: JBIDE-22605 > URL: https://issues.jboss.org/browse/JBIDE-22605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work. > In one instance of Eclipse, stopping such server didn't work. > But then I tried in devstudio and it worked, so I assumed it was some glitch. > But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA. > From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine. > One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup: > {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code} > (Let me know if you want an additional JIRA for that.) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-112) [debug] Better JavaScript hot replace support for Chromium/V8 debugger [EBZ#488344]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-112?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-112: ------------------------------- Assignee: Ilya Buziuk > [debug] Better JavaScript hot replace support for Chromium/V8 debugger [EBZ#488344] > ----------------------------------------------------------------------------------- > > Key: ERT-112 > URL: https://issues.jboss.org/browse/ERT-112 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > > Current Chrome/V8 debugger contribution supports hot deployment for changed .js file to JavaScript MV running in debug mode. It can be done by selecting action from context menu on changed .js file opened in JS Editor from Debug session virtual file system. > This feature should be supported for editing .js files in eclipse workspace as well. When debugging session is on and .js file is changed IDE should check if it is used in current debugging session and ask if it should be hot deployed to JavaScript VM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-243) "Push Source changes to VM" menu is not visible for virtual file system files [EBZ#495433]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-243?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk reassigned ERT-243: ------------------------------- Assignee: Ilya Buziuk > "Push Source changes to VM" menu is not visible for virtual file system files [EBZ#495433] > ------------------------------------------------------------------------------------------ > > Key: ERT-243 > URL: https://issues.jboss.org/browse/ERT-243 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: 3.8_RC4, Debug, bzira > Fix For: Neon (4.6) RC4 > > > Basically, virtual file system files have ".chromium" extension but shown as ".js" files due to decorator implementation. After applying Bug 491480 "Push source changes to VM" is visible only for js / .chromium files are ignored. > Note: even though the virtual file system is hidden, ".chromium" files are available via step into functionality. This are the files which are not available in the workspace e.g. node.js -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-243) "Push Source changes to VM" menu is not visible for virtual file system files [EBZ#495433]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-243?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk resolved ERT-243. ----------------------------- Resolution: Done > "Push Source changes to VM" menu is not visible for virtual file system files [EBZ#495433] > ------------------------------------------------------------------------------------------ > > Key: ERT-243 > URL: https://issues.jboss.org/browse/ERT-243 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: 3.8_RC4, Debug, bzira > Fix For: Neon (4.6) RC4 > > > Basically, virtual file system files have ".chromium" extension but shown as ".js" files due to decorator implementation. After applying Bug 491480 "Push source changes to VM" is visible only for js / .chromium files are ignored. > Note: even though the virtual file system is hidden, ".chromium" files are available via step into functionality. This are the files which are not available in the workspace e.g. node.js -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-800) Update REST test, add insert procedure test, refactoring

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-800?page=com.atlassian.jira.plugin.... ] stanislav kaleta resolved JBTIS-800. ------------------------------------ Resolution: Done > Update REST test, add insert procedure test, refactoring > -------------------------------------------------------- > > Key: JBTIS-800 > URL: https://issues.jboss.org/browse/JBTIS-800 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-800) Update REST test, add insert procedure test, refactoring

by stanislav kaleta (JIRA)

[ https://issues.jboss.org/browse/JBTIS-800?page=com.atlassian.jira.plugin.... ] stanislav kaleta updated JBTIS-800: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/757 > Update REST test, add insert procedure test, refactoring > -------------------------------------------------------- > > Key: JBTIS-800 > URL: https://issues.jboss.org/browse/JBTIS-800 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.1.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-800) Update REST test, add insert procedure test, refactoring

by stanislav kaleta (JIRA)

stanislav kaleta created JBTIS-800: -------------------------------------- Summary: Update REST test, add insert procedure test, refactoring Key: JBTIS-800 URL: https://issues.jboss.org/browse/JBTIS-800 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.3.0.Final Reporter: stanislav kaleta Assignee: Andrej Podhradsky Fix For: 4.3.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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