July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22650) When starting an OS3 server adapter from scratch, error is reported although connection can be established

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22650?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22650: ------------------------------------------ [~jeffmaury] can you still reproduce this? > When starting an OS3 server adapter from scratch, error is reported although connection can be established > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22650 > URL: https://issues.jboss.org/browse/JBIDE-22650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > ASSERT: create an OS3 connection without password saved > ASSERT: create an OS3 server adapter > EXEC: restart Eclipse > EXEC: start the OS3 server adapter and give correct password > ASSERT: error is reported [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22304: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.4.1.AM3 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22650) When starting an OS3 server adapter from scratch, error is reported although connection can be established

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22650?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22650: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > When starting an OS3 server adapter from scratch, error is reported although connection can be established > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22650 > URL: https://issues.jboss.org/browse/JBIDE-22650 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, server > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Fix For: 4.4.1.AM3 > > Attachments: screenshot-1.png > > > ASSERT: create an OS3 connection without password saved > ASSERT: create an OS3 server adapter > EXEC: restart Eclipse > EXEC: start the OS3 server adapter and give correct password > ASSERT: error is reported [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22626) Updating deployed docker image on OpenShift does not work

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22626: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Updating deployed docker image on OpenShift does not work > --------------------------------------------------------- > > Key: JBIDE-22626 > URL: https://issues.jboss.org/browse/JBIDE-22626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.1.AM3 > > > In JBIDE-22515 was fixed use case when user have an image with specific tag. That works now ok. > But if user deploys image with tag e.g. 0.8 to OpenShift, resources are created for this specific tag. When I am trying to push image with tag 0.9 afterwards, everything finish without an error. No new resources are created, but no existing resources are modified to contain this new image. Deployment config still contains tag 0.8 and thus new deployment is not done. > Basically we need to modify deployment config in such cases to contains newer tag and let OpenShift do all magic and redeploy it. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22066: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Server adapter: Stopping debugging of OpenShift application should get application back to normal state. > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.4.1.AM3 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22597) Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22597?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22597: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Deploy Docker wizard: Deploy docker image to openshift may finish without user being notified > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22597 > URL: https://issues.jboss.org/browse/JBIDE-22597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.1.AM3 > > > When a Docker image is deployed to Openshift and this is an update (Openshift resources already exist), then image is pushed to the registry but no feedback is returned to the user. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22580?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22580: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > 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.AM3 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22618) OpenShift explorer: connection stays loading after cancelling the first attempt to provide the token

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22618?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22618: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > OpenShift explorer: connection stays loading after cancelling the first attempt to provide the token > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22618 > URL: https://issues.jboss.org/browse/JBIDE-22618 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Environment: Fedora 23 > TP: 4.60.x up-to-date > Reporter: Dmitry Bocharov > Fix For: 4.4.1.AM3 > > Attachments: OSExplorerLoading.jpg > > > The bug was found when testing [JBIDE-22471] after [refactoring Openshift 3 UI model |https://github.com/jbosstools/jbosstools-openshift/pull/1217] that was actually fixed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22624) Explorer: connection stays "Loading" after I provided the authentication info

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22624?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22624: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Explorer: connection stays "Loading" after I provided the authentication info > ----------------------------------------------------------------------------- > > Key: JBIDE-22624 > URL: https://issues.jboss.org/browse/JBIDE-22624 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: explorer, openshift_v3 > Fix For: 4.4.1.AM3 > > Attachments: 2016-06-21 at 10-23-04.mp4 > > > EXEC: create a new v3 connection to CDK, don't store the password > EXEC: restart Eclipse > EXEC: in OpenShift Explorer: unfold the connection > ASSERT: connection dialog appears, prompting you to provide the password. > EXEC: provide the password, finish > ASSERT: explorer still displays "Loading..." > EXEC: refresh the connection > ASSERT: explorer now displays the resources -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22243: ------------------------------------- Fix Version/s: 4.4.1.AM3 (was: 4.4.1.AM2) > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM3 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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