GitHub user sudhansu7 opened a pull request:
https://github.com/apache/cloudstack/pull/1795
CLOUDSTACK-9625:Unable to scale VM from any offering to a dynamic offering
1.create a custom service offering.
2.stop the running vm
3.scale the vm offering from small to custom offering by providing
(customcpunumber=4,customcpuspeed=512,custommemory=256)
tried with other values as well.
actual result:
scaleVirtualMachine fails with error and its says enter valid value cpu
core and value should be in between 1 to 2147483647 even though we enter
cpucore as 4
test/integration/component/test_dynamic_compute_offering.py also faling.
Test scale running VM from dynamic offering to dynamic offering ... ===
TestName: test_change_so_running_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT | Status
: FAILED ===
FAIL
Test scale running VM from dynamic offering to dynamic offering ... ===
TestName: test_change_so_running_vm_dynamic_to_dynamic_2_USER_ACCOUNT | Status
: FAILED ===
FAIL
Test scale running VM from dynamic offering to static offering ... ===
TestName: test_change_so_running_vm_dynamic_to_static_1_ADMIN_ACCOUNT | Status
: FAILED ===
FAIL
Test scale running VM from dynamic offering to static offering ... ===
TestName: test_change_so_running_vm_dynamic_to_static_2_USER_ACCOUNT | Status :
FAILED ===
FAIL
Test scale running VM from static offering to dynamic offering ... ===
TestName: test_change_so_running_vm_static_to_dynamic_1_ADMIN_ACCOUNT | Status
: FAILED ===
FAIL
Test scale running VM from static offering to dynamic offering ... ===
TestName: test_change_so_running_vm_static_to_dynamic_2_USER_ACCOUNT | Status :
FAILED ===
FAIL
Test scale running VM from static offering to static offering ... ===
TestName: test_change_so_running_vm_static_to_static_1_ADMIN_ACCOUNT | Status :
FAILED ===
FAIL
Test scale running VM from static offering to static offering ... ===
TestName: test_change_so_running_vm_static_to_static_2_USER_ACCOUNT | Status :
FAILED ===
FAIL
Test scale stopped VM from dynamic offering to dynamic offering ... ===
TestName: test_change_so_stopped_vm_dynamic_to_dynamic_1_ADMIN_ACCOUNT | Status
: FAILED ===
FAIL
Test scale stopped VM from dynamic offering to dynamic offering ... ===
TestName: test_change_so_stopped_vm_dynamic_to_dynamic_2_USER_ACCOUNT | Status
: FAILED ===
FAIL
Test scale stopped VM from dynamic offering to static offering ... ===
TestName: test_change_so_stopped_vm_dynamic_to_static_1_ADMIN_ACCOUNT | Status
: SUCCESS ===
ok
Test scale stopped VM from dynamic offering to static offering ... ===
TestName: test_change_so_stopped_vm_dynamic_to_static_2_USER_ACCOUNT | Status :
SUCCESS ===
ok
Test scale stopped VM from static offering to dynamic offering ... ===
TestName: test_change_so_stopped_vm_static_to_dynamic_1_ADMIN_ACCOUNT | Status
: FAILED ===
FAIL
Test scale stopped VM from static offering to dynamic offering ... ===
TestName: test_change_so_stopped_vm_static_to_dynamic_2_USER_ACCOUNT | Status :
FAILED ===
FAIL
Test scale stopped VM from static offering to static offering ... ===
TestName: test_change_so_stopped_vm_static_to_static_1_ADMIN_ACCOUNT | Status :
SUCCESS ===
ok
Test scale stopped VM from static offering to static offering ... ===
TestName: test_change_so_stopped_vm_static_to_static_2_USER_ACCOUNT | Status :
SUCCESS ===
Root Cause:
ParamUnpackWorker creates a Map\<String, Map\<String,String\>\>, which
should be converted to a Map\<String,String\>.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sudhansu7/cloudstack CLOUDSTACK-9625
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1795.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1795
----
commit e97dda6da3a0222619c044c17c99ff7a577f902f
Author: Sudhansu <[email protected]>
Date: 2016-11-28T18:20:00Z
CLOUDSTACK-9625: Unable to scale VM from any offering to a dynamic offering
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
