[jbosstools-issues] [JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

[Andre Dietisheim (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andre Dietisheim updated JBIDE-23412:
-------------------------------------
    Steps to Reproduce: 
The following steps can be seen in the following screencast:
[^scale-to-shows-old-rc.ogv]
# ASSERT: have an app running (ex. nodejs-example)
# ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently
# ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service.
# ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller)
# EXEC: in OpenShift explorer: select Service pick "Deploy Latest"
# ASSERT: in Properties view: "Deployments" now shows 2 Deployments
# ASSERT: in OpenShift Explorer you now see 2 children/pods
# EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service

Result:
The current number of pods is shown as 0. 
!replicas-0.png!
But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod:
!rc2-replicas-1.png!
The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller.
!rc-1-replicas-0.png!


  was:
# ASSERT: have an app running (ex. nodejs-example)
# ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently
# ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service.
# ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller)
# EXEC: in OpenShift explorer: select Service pick "Deploy Latest"
# ASSERT: in Properties view: "Deployments" now shows 2 Deployments
# ASSERT: in OpenShift Explorer you now see 2 children/pods
# EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service

Result:
The current number of pods is shown as 0. 
!replicas-0.png!
But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod:
!rc-2-replicas-1.png!
The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller.
!rc-1-replicas-0.png!




> Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"
> ----------------------------------------------------------------------------------
>
>                 Key: JBIDE-23412
>                 URL: https://issues.jboss.org/browse/JBIDE-23412
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.4.2.AM2
>            Reporter: Andre Dietisheim
>         Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png
>
>




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)