February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23389: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > OpenShift 3.4 support > --------------------- > > Key: JBIDE-23389 > URL: https://issues.jboss.org/browse/JBIDE-23389 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.3.Final > > > OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it. > cc: [~adietish] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23279) Exception generated when OS 3 connection URL is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23279?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23279: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > Exception generated when OS 3 connection URL is invalid > ------------------------------------------------------- > > Key: JBIDE-23279 > URL: https://issues.jboss.org/browse/JBIDE-23279 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: openshift, openshift_v3 > Fix For: 4.4.3.Final > > > EXEC: launch application wizard via file menu: New > OpenShift > OpenShift application > EXEC: select <New Connection> > EXEC: enter invalid URL in the host field > ASSERT: an com.openshift.restclient.OpenShiftException: Unable to initialize client exception is logged into the console -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23136: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23433) SSL Cerrtificate: create unit-tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23433?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23433: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.AM2) > SSL Cerrtificate: create unit-tests > ----------------------------------- > > Key: JBIDE-23433 > URL: https://issues.jboss.org/browse/JBIDE-23433 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > We should create unit-tests for the partial fix provided in JBIDE-23208 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23417) [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23417?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23417: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.AM2) > [Tests]Deploy image wizard: Should have integration tests for the "Services & Routing Settings" wizard page > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23417 > URL: https://issues.jboss.org/browse/JBIDE-23417 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Labels: deploy_docker_wizard, integration-test, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: services-and-routing-settings-wizard-page.png > > > We should create/add integration tests for the "Services and Routing Settings" wizard page which recently got a new column to set the port for the route added. > !services-and-routing-settings-wizard-page.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23434) Preferences: allow loading & validating old ssl certificates that were stored in default locale

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23434?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23434: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.AM2) > Preferences: allow loading & validating old ssl certificates that were stored in default locale > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23434 > URL: https://issues.jboss.org/browse/JBIDE-23434 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > > In JBIDE-23208 we noticed that ssl certificates were store in system default locale to the preferences. The fix fixated the locale to english. We should allow loading and migrating these old certificates. See https://github.com/jbosstools/jbosstools-openshift/pull/1324 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23434) Preferences: allow loading & validating old ssl certificates that were stored in default locale

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23434?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23434: ------------------------------------- Issue Type: Enhancement (was: Task) > Preferences: allow loading & validating old ssl certificates that were stored in default locale > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23434 > URL: https://issues.jboss.org/browse/JBIDE-23434 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.0.AM1 > > > In JBIDE-23208 we noticed that ssl certificates were store in system default locale to the preferences. The fix fixated the locale to english. We should allow loading and migrating these old certificates. See https://github.com/jbosstools/jbosstools-openshift/pull/1324 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23589) Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23589?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23589: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.AM2) > Integration tests global refactoring: org.jboss.tools.openshift.ui.bot.test > --------------------------------------------------------------------------- > > Key: JBIDE-23589 > URL: https://issues.jboss.org/browse/JBIDE-23589 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Labels: integration, integration_tests, openshift > Fix For: 4.5.0.AM1 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.openshift.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23602) Server adapter: Hot code replace failed dialog has poor usability

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23602?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23602: ------------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.3.AM2) > Server adapter: Hot code replace failed dialog has poor usability > ----------------------------------------------------------------- > > Key: JBIDE-23602 > URL: https://issues.jboss.org/browse/JBIDE-23602 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.0.AM1 > > Attachments: hot-code-replace-failed-2.png > > > steps to reproduce: > # ASSERT: have jboss-helloworld running in OpenShift (create it via eap64-basic-s2i template), the source code for it imported to a workspace project and a server adapter for it > # EXEC: open HelloService and change it to the following: > {code:title=HelloService} > public class HelloService { > private static final String MAGIC_STRING = "42"; > > String createHelloMessage(String name) { > return "Hello " + name + ", the magic string is " + MAGIC_STRING + "!"; > } > } > {code} > and save the editor > Result: > "Hot code replace failed" dialog pops up, which is expected. > !hot-code-replace-failed-2.png! > But it's usability is poor: > * the affected module is not fully shown (half of it cut off) > * there's no margin on the right border of the dialog > * No button is pre-selected so that I can simply hit Return to pick a sane default choice (I have to hit tap to get to the button I want to press or use my mouse). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23603: ------------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.3.AM2) > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017