[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-23030:
-------------------------------------
[~jcantrill]: is this something you could look at?
> 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
> Priority: Critical
>
> 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)
9 years, 7 months
[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-23030:
-----------------------------------
Summary: 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
Priority: Critical
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)
9 years, 7 months
[JBoss JIRA] (ERT-401) Include Docker containers in Hierarchy view [EBZ#499749]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-401:
---------------------------------------
Summary: Include Docker containers in Hierarchy view [EBZ#499749]
Key: ERT-401
URL: https://issues.jboss.org/browse/ERT-401
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
The Docker Image hierarchy view should also include the containers based on the images. This is a good way to understand the relationship between containers and images, IMO.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23029:
-------------------------------------
Description:
We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
This is even more true since running the whole suite is a lengthy task.
was:
We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
> This is even more true since running the whole suite is a lengthy task.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23029) Integration tests: Tests should be able to run individually
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23029?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23029:
-------------------------------------
Labels: integration_tests (was: )
> Integration tests: Tests should be able to run individually
> -----------------------------------------------------------
>
> Key: JBIDE-23029
> URL: https://issues.jboss.org/browse/JBIDE-23029
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> We should be able to run the bot tests individually. Currently you cant because the suite is setting up requirements (ex. ScalingTest requires a connection. The connection though is set up in the CreateNewConnectionTest. You thus cant run ScalingTest only, you need to copy the suite, comment all the tests that you dont need).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23026) Integration tests: improve test stability
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23026?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23026:
-------------------------------------
Labels: integration_tests (was: )
> Integration tests: improve test stability
> -----------------------------------------
>
> Key: JBIDE-23026
> URL: https://issues.jboss.org/browse/JBIDE-23026
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.1.AM3
> Reporter: Andre Dietisheim
> Labels: integration_tests
> Fix For: 4.4.x
>
>
> There are several impediments to the test stability:
> * tests dont set up their env individually
> * some tests assert the oc binary, but this binary is not the same across platforms (oc, oc.exe, etc): org.jboss.tools.openshift.reddeer.requirement.OCBinary et org.jboss.tools.openshift.reddeer.utils.OpenShiftLabel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months