June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23902) Support Swarm stack

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23902?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23902: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Support Swarm stack > ------------------- > > Key: JBIDE-23902 > URL: https://issues.jboss.org/browse/JBIDE-23902 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, server_adapter > Fix For: 4.5.0.Final > > > We should support for Widfly Swarm stacks in OpenShift tooling -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24549) Explorer: Add a decorating icon when a build fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24549?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24549: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM2) > Explorer: Add a decorating icon when a build fails > -------------------------------------------------- > > Key: JBIDE-24549 > URL: https://issues.jboss.org/browse/JBIDE-24549 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Jeff MAURY > Labels: explorer, openshift, openshift_v3 > Fix For: 4.5.0.Final > > > When a build fails it should be interesting that it should be visually represented to the user through a decorating icon. As of yet, only the text status is changed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24448) Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24448?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24448: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Application wizard: error decoration is not removed when I correct "Custom Template" url to be valid > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-24448 > URL: https://issues.jboss.org/browse/JBIDE-24448 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Environment: Win 10. > Reporter: Radim Hopp > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.5.0.Final > > > Error decorator is not redrawn until windows is resized. > See screencast: https://youtu.be/BQo-NtDS_c0 > For more detailed info, see JBIDE-23473 > I tried it on Win10 & Fedora 25.... Win10 has this issue, Fedora 25 does not. > Mac is not affected either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24436) Deploy wizard: dialog expands to full available vertical space

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24436?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24436: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Deploy wizard: dialog expands to full available vertical space > -------------------------------------------------------------- > > Key: JBIDE-24436 > URL: https://issues.jboss.org/browse/JBIDE-24436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: deploy-image-wizard-too-tall.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24436) Deploy wizard: dialog expands to full available vertical space

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24436?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24436: ------------------------------------- Steps to Reproduce: (was: # ASSERT: have a docker image available in your local docker daemon # ASSERT: have docker tooling installed and a connection to your local docker daemon defined # EXEC: open "Docker Explorer" view, unfold "Images" for the conneciton to your local docker daemon # EXEC: select your docker image and pick "Deploy to OpenShift..." Result: Docker Image deploy wizard pops up, taking all the available vertical space !deploy-image-wizard-too-tall.png! ) > Deploy wizard: dialog expands to full available vertical space > -------------------------------------------------------------- > > Key: JBIDE-24436 > URL: https://issues.jboss.org/browse/JBIDE-24436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: deploy-image-wizard-too-tall.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24436) Deploy wizard: dialog expands to full available vertical space

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24436?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24436: ------------------------------------- Description: steps: # ASSERT: have a docker image available in your local docker daemon # ASSERT: have docker tooling installed and a connection to your local docker daemon defined # EXEC: open "Docker Explorer" view, unfold "Images" for the conneciton to your local docker daemon # EXEC: select your docker image and pick "Deploy to OpenShift..." Result: Docker Image deploy wizard pops up, taking all the available vertical space !deploy-image-wizard-too-tall.png! > Deploy wizard: dialog expands to full available vertical space > -------------------------------------------------------------- > > Key: JBIDE-24436 > URL: https://issues.jboss.org/browse/JBIDE-24436 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: deploy-image-wizard-too-tall.png > > > steps: > # ASSERT: have a docker image available in your local docker daemon > # ASSERT: have docker tooling installed and a connection to your local docker daemon defined > # EXEC: open "Docker Explorer" view, unfold "Images" for the conneciton to your local docker daemon > # EXEC: select your docker image and pick "Deploy to OpenShift..." > Result: > Docker Image deploy wizard pops up, taking all the available vertical space > !deploy-image-wizard-too-tall.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24441) Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24441?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24441: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Import wizard: "Do not clone - use existing repository" still enabled even though no repo exists > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24441 > URL: https://issues.jboss.org/browse/JBIDE-24441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Priority: Minor > Labels: import_wizard, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: image-2017-05-15-11-26-27-131.png, image-2017-05-15-11-31-02-611.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20397: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Priority: Minor > Labels: application_wizard, openshift_v3, port_forwarding_wizard > Fix For: 4.5.0.Final > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20405) Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20405?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20405: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20405 > URL: https://issues.jboss.org/browse/JBIDE-20405 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Priority: Minor > Labels: connection_wizard, help_wanted, openshift_v3 > Fix For: 4.5.0.Final > > Attachments: Screenshot-4.png, Screenshot-5.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > See attached screenshots - can we provide a more descriptive, and better formatted, error message? Thx! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23710: ------------------------------------- Fix Version/s: 4.5.0.Final (was: 4.5.0.AM1) > Properites: Disable scaling on completed deployments > ---------------------------------------------------- > > Key: JBIDE-23710 > URL: https://issues.jboss.org/browse/JBIDE-23710 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > Fix For: 4.5.0.Final > > > In web console, scaling completed deployments is disabled. > In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift. > Sometimes I also got this exception (but not allways): > {noformat} > !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562 > !MESSAGE Unable to scale wildfly-1 > !STACK 0 > com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114) > at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65) > at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190) > at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163) > at okhttp3.RealCall.execute(RealCall.java:57) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194) > at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183) > at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275) > at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451) > at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {noformat} > I think we should do the same as web console -> disable scaling options on completed deployments. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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