[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
[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
[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