July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22608) Support scenario when cdk is stopped from cli and then in devstudio

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22608?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22608: -------------------------------- Story Points: 3 > Support scenario when cdk is stopped from cli and then in devstudio > ------------------------------------------------------------------- > > Key: JBIDE-22608 > URL: https://issues.jboss.org/browse/JBIDE-22608 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > > Assume your cdk is started and it's shown as started in devstudio, now what if you stop cdk from cli for whatever reason? Currently the tooling can't handle such situation. > If you then try to stop cdk in devstudio, you get an error pop-up: > Server Container Development Environment failed to stop. > And the console will just say: > ==> default: VM not created. Moving on... > But most importantly, the server adapter will stay in the Started state. > We should probably support this scenario - it's quite likely that it will happen to users. > Right now there are several ways out of this situation: > a) Start cdk from cli again and everything will probably work as expected > b) Restart your IDE > So I suggest we improve the tooling in such a way that when you stop cdk, it will be able to detect that it's actually not running and just change the state to Stopped. It may be still ok to pop up the error saying it failed to stop. But at least you can now start it again from the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22664) Invalid registry URL when OS3 connection created by CDK server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22664?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22664: -------------------------------- Story Points: 5 > Invalid registry URL when OS3 connection created by CDK server > -------------------------------------------------------------- > > Key: JBIDE-22664 > URL: https://issues.jboss.org/browse/JBIDE-22664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.1.AM2 > > Attachments: screenshot-1.png > > > When the OS3 connection is created when launching the CDK server, then the Docker registry URL is not valid (garbage characters at the end). This may be a Windows problem. The CDK version used what CDK 2.1RC5 (see [^screenshot-1.png]) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22269) Work with WildFly/EAP to generate unit tests on server installation layout

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22269: -------------------------------- Story Points: 4 > Work with WildFly/EAP to generate unit tests on server installation layout > -------------------------------------------------------------------------- > > Key: JBIDE-22269 > URL: https://issues.jboss.org/browse/JBIDE-22269 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM1 > > > A task to track work on making sure changes to EAP don't inadvertently break tools when changing directory structure or important keys we read. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22675) Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title

by Dmitry Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22675?page=com.atlassian.jira.plugi... ] Dmitry Bocharov updated JBIDE-22675: ------------------------------------ Story Points: 2 > Server Adapter Wizard: Wizard opened via OpenShift Explorer does not have title > ------------------------------------------------------------------------------- > > Key: JBIDE-22675 > URL: https://issues.jboss.org/browse/JBIDE-22675 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Priority: Minor > Labels: openshift_v3, server_adapter_wizard > > OpenShift 3 Server adapter wizard opened from context menu of a service in OpenShift Explorer view does not have title. Shell has title "". Server adapter wizard opened via Servers view or through shell menu File - New does have title "New Server" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22580: -------------------------------- Sprint: (was: devex #116 June 2016) > Deploy Docker Image wizard: Cannot push already tagged image to docker registry > ------------------------------------------------------------------------------- > > Key: JBIDE-22580 > URL: https://issues.jboss.org/browse/JBIDE-22580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.AM1 > > > There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace > {code}Failed to push the selected Docker image into OpenShift registry > org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65) > 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} > I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22580) Deploy Docker Image wizard: Cannot push already tagged image to docker registry

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22580: -------------------------------- Sprint: devex #117 July 2016 > Deploy Docker Image wizard: Cannot push already tagged image to docker registry > ------------------------------------------------------------------------------- > > Key: JBIDE-22580 > URL: https://issues.jboss.org/browse/JBIDE-22580 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.AM1 > > > There is a CDK docker registry located at hub.openshift.rhel-cdk.10.1.2.2.xip.io. From command line user has to tag image at first before pushing it to remote registry to match registry URL, e.g. to push image msa/helloworld from local repository to CDK docker registry I have to tag image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld and then I can just push it "docker push hub.openshift.rhel-cdk.10.1.2.2.xip.io/msa/helloworld". Users used to command line tooling and not aware of "auto-tag" feature of OpenShift tooling can bump into issues. When I am trying to push already tagged image (as I would be expecting from command line) I get an error with following stack trace > {code}Failed to push the selected Docker image into OpenShift registry > org.eclipse.linuxtools.docker.core.DockerException: Conflict: Tag latest is already set to image 2e0ddd37ace80cf13a9d3c664445430972fb3440661eb5d8efb7cc994f11bbdb, if you want to replace it, please use -f option > at org.eclipse.linuxtools.internal.docker.core.DockerConnection.tagImage(DockerConnection.java:1083) > at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:65) > 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} > I think it would be better at first try to check, whether an image does not already have specific tag and if it does, then we should involve confirmation dialog to use force push. If there is no such tagged image, push would behave as it is. Alternatively after checking of image existence we could just simply ignore it, because it is being tagged on same tag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-250?page=com.atlassian.jira.plugin.sy... ] Fred Bricon updated ERT-250: ---------------------------- Sprint: devex #117 July 2016 > Cannot deploy image from local repository to remote registry [EBZ#495793] > ------------------------------------------------------------------------- > > Key: ERT-250 > URL: https://issues.jboss.org/browse/ERT-250 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Critical > Labels: Docker, bzira > > I have a docker connection to local host and a remote registry account in Registry Accounts preference page. For better understanding there is my setup: > - docker host running on local machine (socket at /var/run/docker.sock) > - registry at hub.openshift.rhel-cdk.10.1.2.2.xip.io > - copied registry certificate to local machine to folder /etc/docker/certs.d/hub.openshift.rhel-cdk.10.1.2.2.xip.io/ca.crt (this is necessary because it is docker registry with self-signed certificate and not running with --insecure-registry) > - any local docker image (build locally, not presented on docker hub) > When I am working from command line I do following: > - log in to docker registry hub.openshift.rhel-cdk.10.1.2.2.xip.io with credentials (certificate of docker registry must be present on local machine) > - tag a docker image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha > - push the tagged image to registry > When I am working from IDE with docker tools, I select context menu item Push in the context menu of a docker image and select the registry. At first it is trying to push layers to registry but in the end I get following error without any stack trace > "com.spotify.docker.client.DockerException: > org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha:latest: unknown: request access to the resource is denied". > With docker client from command line everything works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-250) Cannot deploy image from local repository to remote registry [EBZ#495793]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/ERT-250?page=com.atlassian.jira.plugin.sy... ] Fred Bricon updated ERT-250: ---------------------------- Sprint: (was: devex #116 June 2016) > Cannot deploy image from local repository to remote registry [EBZ#495793] > ------------------------------------------------------------------------- > > Key: ERT-250 > URL: https://issues.jboss.org/browse/ERT-250 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Roland Grunberg > Priority: Critical > Labels: Docker, bzira > > I have a docker connection to local host and a remote registry account in Registry Accounts preference page. For better understanding there is my setup: > - docker host running on local machine (socket at /var/run/docker.sock) > - registry at hub.openshift.rhel-cdk.10.1.2.2.xip.io > - copied registry certificate to local machine to folder /etc/docker/certs.d/hub.openshift.rhel-cdk.10.1.2.2.xip.io/ca.crt (this is necessary because it is docker registry with self-signed certificate and not running with --insecure-registry) > - any local docker image (build locally, not presented on docker hub) > When I am working from command line I do following: > - log in to docker registry hub.openshift.rhel-cdk.10.1.2.2.xip.io with credentials (certificate of docker registry must be present on local machine) > - tag a docker image as follows hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha > - push the tagged image to registry > When I am working from IDE with docker tools, I select context menu item Push in the context menu of a docker image and select the registry. At first it is trying to push layers to registry but in the end I get following error without any stack trace > "com.spotify.docker.client.DockerException: > org.eclipse.linuxtools.docker.core.DockerImagePushFailedException: Image push failed: hub.openshift.rhel-cdk.10.1.2.2.xip.io/mlabuda/aloha:latest: unknown: request access to the resource is denied". > With docker client from command line everything works ok. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22442) Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22442?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22442: -------------------------------- Sprint: (was: devex #116 June 2016) > Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22442 > URL: https://issues.jboss.org/browse/JBIDE-22442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.x > > > When managing forwarding ports, select/unselecting the 'Find free local ports' checkbox makes the UI being unresponsive for several seconds and OS (Windows10 in my case) displaying 'Application not responding. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22442) Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22442?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22442: -------------------------------- Sprint: devex #117 July 2016 > Port Forwarding wizard: When managing forwarding ports, UI is unresponsive when playing with find free local ports > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22442 > URL: https://issues.jboss.org/browse/JBIDE-22442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift_v3, port_forwarding_wizard > Fix For: 4.4.x > > > When managing forwarding ports, select/unselecting the 'Find free local ports' checkbox makes the UI being unresponsive for several seconds and OS (Windows10 in my case) displaying 'Application not responding. -- 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