[jbosstools-issues] [JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

Scaling a service changes the wrong deployment ---------------------------------------------- Key: JBIDE-23030 URL: https://issues.jboss.org/browse/JBIDE-23030 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Fred Bricon Assignee: Jeff Cantrill Priority: Critical Fix For: 4.4.2.AM3 Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. The workaround is to open the properties view and issue a scale command on a deployment directly. However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP (copied from JBIDE-23412) 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!