October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23358) OpenShift Explorer: Pod status is not reflecting reality

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23358: ------------------------------------- Summary: OpenShift Explorer: Pod status is not reflecting reality Key: JBIDE-23358 URL: https://issues.jboss.org/browse/JBIDE-23358 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Marián Labuda When I have a pod with failed status, it is not correctly displayed in tooling. Pod under a service has status Running (as styled next next to tree item as well as property value in property view). Current status is failed, precisely "Crash loop back off" (happens often when there are problems with fetching an image...). The correct status is shown in Web-UI as well as from oc binary "oc get pods". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23293) [Forge]When creating a new project, it would be nice to prefill project location by the workspace path

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23293?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-23293: ------------------------------------ Fix Version/s: 4.4.x > [Forge]When creating a new project, it would be nice to prefill project location by the workspace path > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23293 > URL: https://issues.jboss.org/browse/JBIDE-23293 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Fix For: 4.4.x > > Attachments: screenshot-1.png > > > it is currently the user home > !screenshot-1.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23292) Forge is not using Jboss Tools-> remote repositories configuration

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23292?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-23292: ------------------------------------ Fix Version/s: 4.4.x > Forge is not using Jboss Tools-> remote repositories configuration > ------------------------------------------------------------------ > > Key: JBIDE-23292 > URL: https://issues.jboss.org/browse/JBIDE-23292 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Fix For: 4.4.x > > > I configured JBoss Tools -> Remote Repositories and tried to install the addon org.jboss.fuse.forge.addon:fuse-forge,1.0.0.redhat-000013 > which requires one of these repositories http://repository.jboss.org/nexus/content/groups/ea or https://intranet.acme.com/nexus/content/repositories/jboss-eap-6.x-maven-... > I need to modify my settings.xml to include the repository to have it working -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21923) Import application: allow import in context menu of Connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21923?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21923. --------------------------------- Verified in DevStudio 10.2.0.AM2 build AM2-v20161014-0456-B6202. > Import application: allow import in context menu of Connection > -------------------------------------------------------------- > > Key: JBIDE-21923 > URL: https://issues.jboss.org/browse/JBIDE-21923 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: import_wizard > Fix For: 4.4.2.AM2 > > Attachments: ImportApplication.png, jbide-21923.patch > > > In JBIDE-21645 context menu item to import an application was removed from context menu of an OpenShift 3 connection. We should add context menu item back and fix it to let user choose desired build config to import. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-22767: ---------------------------------- Fix Version/s: 4.4.2.Final (was: 4.4.2.AM2) > Deploy Docker Wizard: Create image stream contains wrong tags in some cases > --------------------------------------------------------------------------- > > Key: JBIDE-22767 > URL: https://issues.jboss.org/browse/JBIDE-22767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.2.Final > > > In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). > Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. > Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23357?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-23357: ---------------------------------- Labels: deploy_docker_wizard openshift_v3 (was: ) > Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23357 > URL: https://issues.jboss.org/browse/JBIDE-23357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > > When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23310) Provide IDE meta-files in source code

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23310?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23310: ----------------------------------------- > Did you choose to import as Maven projects (Right click the project -> Update Maven Configuration)? Yes > What projects are you trying to import? All Eclipse Forge plugins that are here: https://github.com/jbosstools/jbosstools-forge > When importing eclipse plugin projects, as maven projects, you need to have the m2eclipse tycho integration first (see Preference > Maven > Discovery) i have Tycho Project Configurators 0.8.0.201409231215 org.sonatype.tycho.m2e.feature.feature.group Sonatype, Inc. To be honest, m2e issue or not, it is always better to commit ide metafiles: I gave a talk about that, hope that it can help you to understand why I really think that it is better: https://www.youtube.com/watch?v=J5RzSbpNLM4 > Provide IDE meta-files in source code > ------------------------------------- > > Key: JBIDE-23310 > URL: https://issues.jboss.org/browse/JBIDE-23310 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge > Reporter: Aurélien Pupier > > it will help other contributors to setup the environment -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23357) Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-23357: ------------------------------------- Summary: Deploy Docker Wizard: Image is not revalidated if going back to Deploy an Image wizard page Key: JBIDE-23357 URL: https://issues.jboss.org/browse/JBIDE-23357 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.2.AM2 Reporter: Marián Labuda When I fill in valid image into the wizard and hit next, there is a check on existence of such image and its metadata are fetched. Problem is when I go back to the Deploy an Image wizard page and put there invalid image name. Finish button is still enabled and it allows user to use non-existing (made-up) image to deploy. It results in wrong deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22916) Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-22916. --------------------------------- Verified in DevStudio 10.2.0.AM2 build AM2-v20161014-0456-B6202. > Deploy Docker Wizard: Deploying a docker image from OpenShift explorer does not fetch metadata if image is not pulled to a docker connection > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22916 > URL: https://issues.jboss.org/browse/JBIDE-22916 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: 2016-09-06 at 14-19-31.mp4 > > > When I am trying to deploy a docker image from context menu of a project in OpenShift explorer view and I paste image name (e.g. docker.io/openshift/hello-openshift), image metadata are not fetched/processed and thus there are no environment variables in the wizard and routing (routing wizard page is empty and cannot finish dialog - requires manual entry). This force user to enter the details manually, otherwise he would get deployed not working pod. This is happening only in case when user provide an image without any tag and thus there is/supposed to be assumed tag "latest". > You can observe that it works when using tag v1.2.1. Difference between images with tag v1.2.1 and latest is that v1.2.1 contains exposed ports also in container config, not just in general config of the image. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23319) Pre-configure the OpenShift server adapter

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23319?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23319. --------------------------------- > Pre-configure the OpenShift server adapter > ------------------------------------------ > > Key: JBIDE-23319 > URL: https://issues.jboss.org/browse/JBIDE-23319 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.AM2 > > > When using the Developmen tsuite installer, it preconfigures the CDK adapter. > The CDK instance is providing an OpenShift instance instance, it will be nice to provide the OpenShift adapter for this instance by default -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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