Description of problem: Updating of the serial number policy from custom to VM causes different output - in Get VMs and virsh Version-Release number of selected component (if applicable): rhv-release-4.2.5-5-001.noarch How reproducible:100% Steps to Reproduce: 1.In UI Open EditVM/System. Choose custom serial number policy and enter some value. Start VM. Check virsh dumpxml output and Get vms API output - contain correct values 2.Update the custom policy to the VM ID policy (choose VM ID option in 'Provide custom serial number policy'). ok in the dialog. Restart VM. 3.Check virsh output ( virsh -r dumpxml vm_id ) and get VMS API (https://{{host}}/ovirt-engine/api/vms) Actual results: in virsh output we see the correct result - serial number equals to UUID. <system> .... <entry name='serial'>3855687f-a362-48a9-8d5a-b1dc3ff22dd5</entry> <entry name='uuid'>3855687f-a362-48a9-8d5a-b1dc3ff22dd5</entry> </system> In rest API response we see the previous value for serial number: <serial_number> <policy>vm</policy> <value>4567</value> </serial_number> Expected results: Rest API response must not contain the previous serial number value <value>4567</value> Additional info:
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-14
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.