[jbosstools-issues] [JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
[
https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-23030:
---------------------------------------
[~fbricon] You will need to remind me where the initial issue was for this. It was when I
attempted to scale and started from the deploymentconfig? or i right-click on a service
and scale?
Scaling a service changes the wrong deployment
----------------------------------------------
Key: JBIDE-23030
URL: https://issues.jboss.org/browse/JBIDE-23030
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.4.1.AM3
Reporter: Fred Bricon
Assignee: Jeff Cantrill
Priority: Critical
Fix For: 4.4.2.AM3
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
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)