January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23474) Fix jbt-server otherOS test cases

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23474?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23474: ------------------------------------- pushed to master > Fix jbt-server otherOS test cases > --------------------------------- > > Key: JBIDE-23474 > URL: https://issues.jboss.org/browse/JBIDE-23474 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.2.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_mas... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3869) DevSuite Installer should check/warn if Hyper-V is already enabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3869: -------------------------------- Summary: DevSuite Installer should check/warn if Hyper-V is already enabled (was: platform installer should check/warn if Hyper-V is already enabled) > DevSuite Installer should check/warn if Hyper-V is already enabled > ------------------------------------------------------------------ > > Key: JBDS-3869 > URL: https://issues.jboss.org/browse/JBDS-3869 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 10 Pro, 64 bit. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 10.3.0.AM2 > > > The platform installer should check and warn if Hyper-V is already enabled on Windows systems. > Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4240) Update Oracle Virtualbox to 5.1.12 for macOS and Windows

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4240: ----------------------------------- Summary: Update Oracle Virtualbox to 5.1.12 for macOS and Windows Key: JBDS-4240 URL: https://issues.jboss.org/browse/JBDS-4240 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.3.0.AM2 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.3.0.AM2 Latest version of Virtualbox is required to work with minishift. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4239) CDK 3 Installer for Windows using Virtualbox

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4239?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4239: -------------------------------- Summary: CDK 3 Installer for Windows using Virtualbox (was: CDK 3 Installer) > CDK 3 Installer for Windows using Virtualbox > -------------------------------------------- > > Key: JBDS-4239 > URL: https://issues.jboss.org/browse/JBDS-4239 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > > Vagrant is not required anymore and should be removed. > minishift and new iso image should be included. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23711: ------------------------------------- Fix Version/s: 4.4.3.AM2 > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > 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.4.3.AM2 > > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23711: ------------------------------------- Labels: openshift_v3 properties (was: ) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > Labels: openshift_v3, properties > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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: ------------------------------------- Summary: Properites: Disable scaling on completed deployments (was: Disable scaling on completed deployments) > 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.4.3.AM2 > > > 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)

9 years, 2 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: ------------------------------------- Labels: openshift_v3 properties (was: ) > 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.4.3.AM2 > > > 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)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23711) Properites: "Edit default route" on Build config does nothing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23711?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23711: ------------------------------------- Summary: Properites: "Edit default route" on Build config does nothing (was: "Edit default route" on Build config does nothing) > Properites: "Edit default route" on Build config does nothing > ------------------------------------------------------------- > > Key: JBIDE-23711 > URL: https://issues.jboss.org/browse/JBIDE-23711 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Radim Hopp > > Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23710) 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: ------------------------------------- Story Points: 2 > 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 > Fix For: 4.4.3.AM2 > > > 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)

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