[jbosstools-issues] [JBoss JIRA] (JBIDE-25273) Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"
Andre Dietisheim (JIRA)
issues at jboss.org
Fri Oct 20 08:28:06 EDT 2017
[ https://issues.jboss.org/browse/JBIDE-25273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andre Dietisheim updated JBIDE-25273:
-------------------------------------
Description:
steps:
# ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template)
# ASSERT: make sure that your memory request limit is in bytes:
# EXEC: in OpenShift explorer, select your project
# EXEC: in "Properties" view, select "Deployments" tab and select the last entry
# EXEC: pick "Edit" in the context menu to it
# ASSERT: replication controller is opened in the editor
# EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit
{code}
"resources" : {
"limits" : {"memory" : "512"},
},
{code}
# EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu
# ASSERT: Edit resource limits wizard shows up
Result:
Memory > Limits show *MiB* as unit
!edit-resource-limits-memory-limit-units.png!
was:
steps:
# ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template)
# ASSERT: make sure that your memory request limit is in bytes:
# EXEC: in OpenShift explorer, select your project
# EXEC: in "Properties" view, select "Deployments" tab and select the last entry
# EXEC: pick "Edit" in the context menu to it
# ASSERT: replication controller is opened in the editor
# EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit
{code}
"resources" : {
"limits" : {"memory" : "512"},
},
{code}
# EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu
# ASSERT: Edit resource limits wizard shows up
Result:
Memory > Limits show *MiB* as unit
> Edit resource limits wizard: memory limit is erroneously shown as "MiB" where it should be "bytes"
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25273
> URL: https://issues.jboss.org/browse/JBIDE-25273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.1.AM3
> Reporter: Andre Dietisheim
> Labels: edit_resource_limits_wizard, openshift_v3
> Fix For: 4.5.1.Final
>
> Attachments: edit-resource-limits-memory-limit-units.png
>
>
> steps:
> # ASSERT: make sure that you have an application with a service and replication controller running in OpenShift (ex. create an app with the nodejs-mongo-persistent template)
> # ASSERT: make sure that your memory request limit is in bytes:
> # EXEC: in OpenShift explorer, select your project
> # EXEC: in "Properties" view, select "Deployments" tab and select the last entry
> # EXEC: pick "Edit" in the context menu to it
> # ASSERT: replication controller is opened in the editor
> # EXEC: search (Ctrl+F) "limits" and make sure it has an entry for memory limits that has no unit
> {code}
> "resources" : {
> "limits" : {"memory" : "512"},
> },
> {code}
> # EXEC: in OpenShift Explorer: select the service for your application and pick "Edit Resource Limits..." in the context menu
> # ASSERT: Edit resource limits wizard shows up
> Result:
> Memory > Limits show *MiB* as unit
> !edit-resource-limits-memory-limit-units.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbosstools-issues
mailing list