June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20972) As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20972?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20972: ------------------------------------- Issue Type: Enhancement (was: Feature Request) > As a user I want to see relevant but simple info about my OpenShift v3 server adapter in the servers view > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20972 > URL: https://issues.jboss.org/browse/JBIDE-20972 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Jeff Cantrill > Labels: explorer, openshift_v3 > Fix For: 4.4.x > > Attachments: 2015-10-13 19.03.bmml, 2015-10-13 19.03.png, Console of 'App' with the pieces wired.png, Pipeline view mockup.bmml > > > Add an alternate view in the openshift v3 explorer to try to 'link' resources in a similiar fashion to the web console -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21666) Properties view: Set correct OpenShift resource name for Repplication controller in properties view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21666?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21666: ------------------------------------- Issue Type: Enhancement (was: Bug) > Properties view: Set correct OpenShift resource name for Repplication controller in properties view > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-21666 > URL: https://issues.jboss.org/browse/JBIDE-21666 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, properties > Fix For: 4.4.x > > > At the moment we have following OpenShift resources listed for a project in Properties view: > * Builds > * Build Configs > * Deployment Configs > * Pods > * Deployments > * Image Streams > * Routes > * Services > What is misleading is having "Deployment Configs" and "Deployments". We are trying to copy web-UI, as far as I know. But in the web-UI under Deployments are placed "Deployment Configs". We, under "Deployments" in properties view, have "Replication Controllers". So its misleading for me. I think we should rename our Deployment Configs to Deployment and our Deployments to Replication Controllers, which are missing in web-ui because the most significant functionality accessible via Replication Controllers is editable in web-ui through overview page (e.g spinner for amount of pods). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-783) Fuse: Add regression test for FUSETOOLS-1211

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-783: ---------------------------------- Summary: Fuse: Add regression test for FUSETOOLS-1211 Key: JBTIS-783 URL: https://issues.jboss.org/browse/JBTIS-783 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík https://issues.jboss.org/browse/FUSETOOLS-1211 test switching between different routes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-782) Fuse: Add tests for Server Runtime Overview Page

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-782: ---------------------------------- Summary: Fuse: Add tests for Server Runtime Overview Page Key: JBTIS-782 URL: https://issues.jboss.org/browse/JBTIS-782 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík see Servers View --> (select a server) --> select Open option in the context menu also review DeploymentTest - testImmeadiatelyPublishing: * publishing options are in Server Runtime Overview Page -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-781) Fuse: Extend 'DownloadServerTest'

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-781: ---------------------------------- Summary: Fuse: Extend 'DownloadServerTest' Key: JBTIS-781 URL: https://issues.jboss.org/browse/JBTIS-781 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Priority: Minor check: server can be started version is correct try to download all available runtimes https://issues.jboss.org/browse/FUSETOOLS-1383 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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: ------------------------------------- Labels: deploy_docker_wizard docker openshift_v3 (was: docker openshift_v3) > 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: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Labels: deploy_docker_wizard, docker, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > 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, 10 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: ------------------------------------- Summary: Deploy Docker Image wizard: Cannot push already tagged image to docker registry (was: Cannot push already tagged image to docker registry) > 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: openshift > Affects Versions: 4.4.0.Final > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.1.Alpha1 > > > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22592) Application wizard: Failed even though provided required value to parameters

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22592?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22592: ------------------------------------- Summary: Application wizard: Failed even though provided required value to parameters (was: Application wizard: Failed in setting required value to parameters) > Application wizard: Failed even though provided required value to parameters > ---------------------------------------------------------------------------- > > Key: JBIDE-22592 > URL: https://issues.jboss.org/browse/JBIDE-22592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Environment: JBoss OpenShift 3 Tools 3.3.0.Final-v20160610-1836-B1369 > JBoss OpenShift 3 Tools Developer Resources 3.3.0.Final-v20160610-1836-B1369 > Eclipse: Neon Milestone 7 (4.6.0M7) > Reporter: Xia Zhao > Labels: application_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: application-template-stibuild.json, fails-even-though-required-value-provided.png, Screenshot from 2016-06-12 01-59-02.png > > > Create app from the local template in attachment,give required value to parameter "xiazhao_checkfail" inside new-app wizard, get error message after clicking on the "Next>" button: > Template "ruby-helloworld-sample" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified > Could not create resource ruby-helloworld-sample in namespace 'xiazhao-1': {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Template \"ruby-helloworld-sample\" is invalid: template.parameters[5]: Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","reason":"Invalid","details":{"name":"ruby-helloworld-sample","kind":"Template","causes":[{"reason":"FieldValueRequired","message":"Required value: template.parameters[5]: parameter xiazhao_checkfail is required and must be specified","field":"template.parameters[5]"}]},"code":422} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-780) Fuse: Add test case for endpoint manipulation in JMX Navigator

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-780: ---------------------------------- Summary: Fuse: Add test case for endpoint manipulation in JMX Navigator Key: JBTIS-780 URL: https://issues.jboss.org/browse/JBTIS-780 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík In JMX Navigator View can be created/deleted endpoints (in running Camel context) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-779) Fuse: Add test case for run configurations

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-779: ---------------------------------- Summary: Fuse: Add test case for run configurations Key: JBTIS-779 URL: https://issues.jboss.org/browse/JBTIS-779 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.Final Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Local Camel Context Maven Build -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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