[
https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-23710:
-------------------------------------
Steps to Reproduce:
# EXEC: Create app in OS3
# EXEC: When it is deployed, go to Deployment Configs and click "deploy
latest".
# ASSERT: Wait for deployment to finish (old pods get killed, new pods are running).
# ASSERT: Now there should be two deployments in Properties View->Deployments tab (for
example wildfly-1, wildfly-2, where wildfly-2 is the active, wildfly-1 is the completed
one.
# EXEC: Right click the completed one (wildfly-1), select scale-> scale up. Observe
results.
was:
Create app in OS3
When it is deployed, go to Deployment Configs and click "deploy latest".
Wait for deployment to finish (old pods get killed, new pods are running)
Now there should be two deployments in Properties View->Deployments tab (for example
wildfly-1, wildfly-2, where wildfly-2 is the active, wildfly-1 is the completed one.
Right click the completed one (wildfly-1), select scale-> scale up. Observe results.
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)