I have a problem with re-configure VM (hot plug) CloudForms 4.1


I’m using CloudForms 4.1 and i try to use the control module to automatic-resize a VM if the CPU or the Memory is high, but when the re-configure request is created, the request failed. If i try to make a request in Vmware (with the VM in running state) everything is OK. If i try to re-configure a VM (in running state) in CloudForms i get an error message and the request goes to a fail state. If i shutdown the VM and use the re-configure option in CloudForms, the request works ok. Do you know if is possible to re-configure a VM in running state or feature is not enable in CloudForms?

@DanielBello could you post the error message you receive when trying to make a Vmware request with the VM running.

We were able to add a CPU socket to a running VM that had CPU Hot Add enabled.

There are a few issues that make this not very intuitive with the ManageIQ UI, we don’t verify that you have CPU/Memory Hot Add enabled before allowing you to reconfigure a running VM. We also allow you to add more memory than the hotPlugMemoryLimit which in this case was just 3GB.

We really should have checks in place for these conditions, here is an RFE to track them https://bugzilla.redhat.com/show_bug.cgi?id=1386843

Thanks for your reply. Actually that ticket in bugzilla is about my case in Red Hat :joy:
I’m waiting the reply from support team because i really need this feature available, but at this time Cloudforms is not getting the value when the CPU or RAM is over than 80% (or whatever that i have set as limit) .

I’m actually half done with it :slight_smile:
The PR to collect this data in inventory was merged https://github.com/ManageIQ/manageiq/pull/12145
And I have a PR out to check this at provision time https://github.com/ManageIQ/manageiq/pull/12275
If you want to test that’d be awesome, and we are working on the BZ for your other issue https://bugzilla.redhat.com/show_bug.cgi?id=1387790

Well, thanks for your efforts in the bugzilla, but the ticket was marked as “not a bug”. Actully the response of support team was that in this release the metrics only are getting and showing information about 30 days and my requirement is not supported in this release. For me, the control module in this case is useless and only works fine for alerting.