New commit detected on ManageIQ/manageiq-providers-ovirt/gaprindashvili:
Author: Piotr Kliczewski <email@example.com>
AuthorDate: Thu Aug 30 03:14:30 2018 -0400
Commit: Piotr Kliczewski <firstname.lastname@example.org>
CommitDate: Thu Aug 30 03:14:30 2018 -0400
Merge pull request #280 from fdupont-redhat/add_support_for_vm_set_memory_and_cpus
Add support to set VM memory and number of CPUs
(cherry picked from commit c1c4cb7ecd9a013eacbec6f2835e54fc321a2f58)
app/models/manageiq/providers/redhat/infra_manager.rb | 13 +
spec/models/manageiq/providers/redhat/infra_manager_spec.rb | 21 +
2 files changed, 34 insertions(+)
New commit detected on ManageIQ/manageiq-automation_engine/gaprindashvili:
Author: Greg McCullough <email@example.com>
AuthorDate: Thu Aug 30 08:12:06 2018 -0400
Commit: Greg McCullough <firstname.lastname@example.org>
CommitDate: Thu Aug 30 08:12:06 2018 -0400
Merge pull request #216 from fdupont-redhat/redhat_vm_add_support_for_set_memory_and_cpus
Add support to redhat VM for set_memory and set_number_of_cpus
(cherry picked from commit bef5fc5e930ecc9b77f6b829f914c8948eaa0c3f)
lib/miq_automation_engine/service_models/miq_ae_service_manageiq-providers-redhat-infra_manager-vm.rb | 8 +
spec/service_models/miq_ae_service_manageiq-providers-redhat-infra_manager-vm_spec.rb | 22 +
2 files changed, 30 insertions(+)
Verified on CFME-5.9.5/RHV-4.2.3
Followed these verification steps from the cloned bug 1623021:
To check this feature is working as expected, one can use Rails console:
# rails c
irb> $evm = MiqAeMethodService::MiqAeService.new(MiqAeEngine::MiqAeWorkspaceRuntime.new)
For example, you want to change the CPU and memory of a VM named 'test_vm'. Here are the command to execute in Rails console:
irb> vm = $evm.vmdb(:vm).find_by(:name => 'test_vm')
Then, you should see in your RHV environment that VM named 'test_vm' has 2 vCPUs and 4 GB of memory.
It was run on a Down VM with 2G Memory, and 1 vCPU.
After running the Rails commands, VM was updated to 4G Memory and 2 vCPUs.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.