September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23020) Integration tests: Have a dedicated OS instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23020?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23020: ------------------------------------- Story Points: 4 > Integration tests: Have a dedicated OS instance > ----------------------------------------------- > > Key: JBIDE-23020 > URL: https://issues.jboss.org/browse/JBIDE-23020 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.x > > > We dont have a dedicated OS instance for the integration tests. > Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. > Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 3 days > Remaining Estimate: 3 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22451) Tests: Improve test coverage in OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22451?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22451: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Tests: Improve test coverage in OpenShift > ----------------------------------------- > > Key: JBIDE-22451 > URL: https://issues.jboss.org/browse/JBIDE-22451 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > > Test coverage in OpenShift is far too poor. We have to increase it dramatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23036) Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23036?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23036: ---------------------------------------- Is this issue still relevant? Should we close it? > Move Docker/Vagrant Tooling from target platform to jbosstools-openshift pom dependency > --------------------------------------------------------------------------------------- > > Key: JBIDE-23036 > URL: https://issues.jboss.org/browse/JBIDE-23036 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, openshift, target-platform > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.x > > > In order to support faster updates to Docker Tooling and to get those changes more frequently into the jbosstools-openshift builds, we should do for Docker Tooling what we did for Tern/Angular: > * document how to perform regular mirrors of the nightly site onto http://download.jboss.org/jbosstools/updates/requirements/docker (using Jenkins job to pull mirror) > * remove docker/vagrant tooling from target platform > * add docker/vagrant mirror site into jbosstools-openshift/pom.xml, with comments/instructions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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.2.AM2 (was: 4.4.2.AM1) > 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 > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: ImageStreamTags.jpg > > > 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 Deploy to OS 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. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. > Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht... > Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > 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 > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: ImageStreamTags.jpg > > > 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 Deploy to OS 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. > In order to add this version tag after semicolon, right-click on the image -> Add tag -> Re-type namespace/imagename + add ":0.8" e.g. > Tagging Images: https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht... > Image Change Trigger: https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23014: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Allow connections to configure the cluster namespace from which to get clusterwide templates > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23014 > URL: https://issues.jboss.org/browse/JBIDE-23014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff Cantrill > Assignee: Jeff MAURY > Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > > There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23014: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Allow connections to configure the cluster namespace from which to get clusterwide templates > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23014 > URL: https://issues.jboss.org/browse/JBIDE-23014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff Cantrill > Assignee: Jeff MAURY > Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > > There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22916?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22916: ------------------------------------- Sprint: devex #119 August 2016, devex #121 October 2016 (was: devex #119 August 2016, devex #120 September 2016) > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23006) OkHttp reports leaked connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23006?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23006: ------------------------------------- Sprint: devex #119 August 2016, devex #121 October 2016 (was: devex #119 August 2016, devex #120 September 2016) > OkHttp reports leaked connections > --------------------------------- > > Key: JBIDE-23006 > URL: https://issues.jboss.org/browse/JBIDE-23006 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff MAURY > Fix For: 4.4.2.AM2 > > > After connecting to an OpenShift instance, some warnings show up in the logs eventually: > {noformat} > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > août 15, 2016 10:55:20 AM okhttp3.internal.Platform log > AVERTISSEMENT: A connection to https://console.dev-preview-stg.openshift.com/ was leaked. Did you forget to close a response body? > {noformat} > I haven't figured out exactly what steps cause these yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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