Bug 1396782 - [Bug RHV4.0.6] After adding new disk, other configuration does not refresh while creating new VM.
Summary: [Bug RHV4.0.6] After adding new disk, other configuration does not refresh wh...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ovirt-4.0.6
: ---
Assignee: Tomas Jelinek
QA Contact: Israel Pinto
URL:
Whiteboard:
Depends On: 1391466
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-20 06:01 UTC by Ulhas Surse
Modified: 2020-02-14 18:18 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Memory leak fixes caused regressions in the flows when one dialog open an another one. Consequence: After opening a new disk dialog from the new vm dialog and than closing the disk dialog, the VM dialog did not work properly (the console / cpu modifications did not behave correctly) Fix: On opening a new disk from new vm dialog, dont close the vm dialog (e.g. both will be shown on top of each other). Result: After closing the disk dialog, the VM dialog will keep working as before.
Clone Of:
Environment:
Last Closed: 2017-01-16 15:42:43 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Ulhas Surse 2016-11-20 06:01:45 UTC 
Description of problem:
While creating new VM, if you create a disk first (press OK twice #bug1396781) and then try to set the  "Total Virtual CPUs" and say 2 vcores -> it change NOT the "Virtual Sockets" in the advanced parameter.

In the "advanced parameters" the virtual sockets stay 1, cores per virtual stay 1 , threads per core stay 1 and the box give only the posibility to select 1 and not 2.

Version-Release number of selected component (if applicable):
RHV 4.0.5

How reproducible:
Always

Steps to Reproduce:
1. Create New VM. 
2. Create new disk (save configuration, press OK twice)  
3. Now go to System -> Total Virtual CPUs -> set any (3,5,4) 
4. It does not reflect in Advanced parameters. 

Actual results:
Advanced parameters are not refreshed for any change in Total Virtual CPU. 

Expected results:
Changes should be reflected as soon as value modified. 

Additional info:
Workaround is available to set after creating VM, edit the VM.
Comment 1 Ulhas Surse 2016-11-20 06:02:35 UTC 
Other workaround is to set these options before creating the disk.
Comment 2 Tomas Jelinek 2016-11-21 08:33:29 UTC 
It looks a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1391466 
moving to UX to confirm.
Comment 3 Oved Ourfali 2016-11-21 13:19:25 UTC 
Greg - is it the same?
Comment 4 Oved Ourfali 2016-11-21 13:19:46 UTC 
Ulhas - can you attach the engine and ui logs?
Comment 5 Alexander Wels 2016-11-21 16:45:03 UTC 
@Oved

It does appear to be the same type of issue, in particular I think the problem is that the new disk dialog closes the new vm dialog, and that triggers the cleanup. I will take a closer look at the exact cause, but it does look the same.
Comment 8 Oved Ourfali 2016-11-28 13:02:49 UTC 
Leaving this for verification purposes.
This should be fixed with the fix for Bug 1391466
Comment 10 Israel Pinto 2016-12-11 13:00:04 UTC 
Verify with:
Engine: 4.0.6.3-0.1.el7ev
Host:
OS Version:RHEL - 7.3 - 7.el7
OS Description:Red Hat Enterprise Linux Server 7.3 (Maipo)
Kernel Version:3.10.0 - 514.el7.x86_64
KVM Version:2.6.0 - 27.el7
LIBVIRT Version:libvirt-2.0.0-10.el7
VDSM Version:vdsm-4.18.16-1.el7ev


steps:
1. Create New VM. 
2. Create new disk (save configuration)  
3. Now go to System -> Total Virtual CPUs -> set any (2,4) 
4. Check that Advanced parameters is updated

Results:
Advanced parameters is updated
Note: also checked other parameters: in Host/Console/Boot options
all are updated.
Comment 11 Anton Marchukov 2017-01-16 15:42:43 UTC 
Fixed in https://rhn.redhat.com/errata/RHBA-2017-0043.html
Note You need to log in before you can comment on or make changes to this bug.