Bug 1388964

Summary: Reconfigure does not modify cpu/mem for rhev or vmware vm's
Product: Red Hat CloudForms Management Engine Reporter: Josh Carter <jocarter>
Component: ProvidersAssignee: Adam Grare <agrare>
Status: CLOSED DUPLICATE QA Contact: luke couzens <lcouzens>
Severity: high Docs Contact:
Priority: high    
Version: 5.7.0CC: cpelland, dajohnso, gblomqui, istein, jfrey, jhardy, jocarter, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard: vm:reconfigure
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-17 15:26:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:

Description Josh Carter 2016-10-26 15:05:38 UTC
Description of problem:

When submitting a increase or decrease of either cpu or mem the task is never submitted or runs in automate. This occurs for both vmware and rhev vm's. 

Version-Release number of selected component (if applicable):
 Version 5.7.0.7-beta1.20161025153249_9376fbd 

rhev-5.7
vmware-5.1

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 5 Adam Grare 2016-10-27 16:04:38 UTC
I just increased the memory on a VM from 4GB to 8GB with 5.7.0.7-beta1.20161025153249_9376fbd to a 6.0 VC and everything worked.

Do you have any logs that show the failure?

Comment 6 Ilanit Stein 2016-11-13 10:01:12 UTC
this bug is probably a duplicate of Bug 1389303 - "[Beta 1] Submit button in Infra>VM Reconfiguration is not working".

This problem started on CFME-5.7.0.7,
and has a work around of using region=0, when configuring the CFME appliance dataBase.

bug 1389303 is expected to be fixed on CFME version, that will follow CFME-5.7.0.10

Comment 7 Adam Grare 2016-11-16 19:00:12 UTC
I did use region 0 for my appliance, let me try re-testing with a non-0 region.  Thanks Ilanit.

Comment 8 Adam Grare 2016-11-17 15:26:00 UTC
I was able to reproduce this issue using region 10 with beta 1 and have confirmed it is fixed in rc1.

*** This bug has been marked as a duplicate of bug 1389303 ***