[JBoss JIRA] (JBIDE-23710) 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:
-------------------------------------
Steps to Reproduce:
# EXEC: Create app in OS3
# EXEC: When it is deployed, go to Deployment Configs and click "deploy latest".
# ASSERT: Wait for deployment to finish (old pods get killed, new pods are running).
# ASSERT: Now there should be two deployments in Properties View->Deployments tab (for example wildfly-1, wildfly-2, where wildfly-2 is the active, wildfly-1 is the completed one.
# EXEC: Right click the completed one (wildfly-1), select scale-> scale up. Observe results.
was:
Create app in OS3
When it is deployed, go to Deployment Configs and click "deploy latest".
Wait for deployment to finish (old pods get killed, new pods are running)
Now there should be two deployments in Properties View->Deployments tab (for example wildfly-1, wildfly-2, where wildfly-2 is the active, wildfly-1 is the completed one.
Right click the completed one (wildfly-1), select scale-> scale up. Observe results.
> 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
> Fix For: 4.4.3.AM2
>
>
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-23710) 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.4.3.AM2
> 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
> Fix For: 4.4.3.AM2
>
>
> 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)
9 years, 2 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-22816.
--------------------------------------
Resolution: Done
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22816:
-------------------------------------
Fix Version/s: 4.4.3.AM1
(was: 4.4.3.AM2)
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22816:
------------------------------------------
[~jeffmaury] thx for the steps. Tried to replicate it but couldnt. Thus resolving it. QE will then close if they cannot reproduce either.
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM1
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4239) CDK 3 Installer
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4239:
-----------------------------------
Summary: CDK 3 Installer
Key: JBDS-4239
URL: https://issues.jboss.org/browse/JBDS-4239
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 10.3.0.AM2
Environment: Windows
Reporter: Denis Golovin
Vagrant is not required anymore and should be removed.
minishift and new iso image should be included.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4239) CDK 3 Installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4239?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4239:
-----------------------------------
Issue Type: Feature Request (was: Task)
Fix Version/s: 10.3.0.AM2
Assignee: Denis Golovin
> CDK 3 Installer
> ---------------
>
> Key: JBDS-4239
> URL: https://issues.jboss.org/browse/JBDS-4239
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.3.0.AM2
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.3.0.AM2
>
>
> Vagrant is not required anymore and should be removed.
> minishift and new iso image should be included.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3869:
--------------------------------
Summary: platform installer should check/warn if Hyper-V is already enabled (was: platform installer should check/warn if Hyper-V is already enabled.)
> platform installer should check/warn if Hyper-V is already enabled
> ------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3869 at 1/10/17 2:10 PM:
--------------------------------------------------------------
Yet better approach is
{code}PS C:\WINDOWS\system32> Get-WindowsOptionalFeature –Online | where FeatureName -eq Microsoft-Hyper-V-All | foreach { $_.
state }{code}
returns
{code}Disabled{code}
or
{code}Disabled{code}
or empty string if feature is not available.
was (Author: dgolovin):
Yet better approach is
{code}Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All{code}
return for Hyper-V enabled and restart is possibly required
{code}FeatureName : Microsoft-Hyper-V-All
DisplayName : Hyper-V
Description : Provides services and management tools for creating and running virtual machines and their resources.
RestartRequired : Possible
State : Enabled
CustomProperties :{code}
> platform installer should check/warn if Hyper-V is already enabled.
> -------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-3869) platform installer should check/warn if Hyper-V is already enabled.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3869:
-------------------------------------
Yet better approach is
{code}Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All{code}
return for Hyper-V enabled and restart is possibly required
{code}FeatureName : Microsoft-Hyper-V-All
DisplayName : Hyper-V
Description : Provides services and management tools for creating and running virtual machines and their resources.
RestartRequired : Possible
State : Enabled
CustomProperties :{code}
> platform installer should check/warn if Hyper-V is already enabled.
> -------------------------------------------------------------------
>
> Key: JBDS-3869
> URL: https://issues.jboss.org/browse/JBDS-3869
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 10 Pro, 64 bit.
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> The platform installer should check and warn if Hyper-V is already enabled on Windows systems.
> Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months