Bug 1956967

Summary: 'Next run config changes' mark appears when nothing was changed on VM
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: Frontend.WebAdminAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: low Docs Contact:
Priority: unspecified    
Version: 4.4.6.6CC: ahadas, bugs
Target Milestone: ovirt-4.4.7Keywords: ZStream
Target Release: 4.4.7Flags: pm-rhel: ovirt-4.4+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-06 07:28:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine.log none

Description Polina 2021-05-04 18:58:17 UTC
Created attachment 1779480 [details]
engine.log

Description of problem:'Next run config changes' mark appears when nothing was changed on VM

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.6.6-0.10.el8ev.noarch

How reproducible:100%

Steps to Reproduce:
1. Configure VM to have 4 CPUs, HighPerformance type, pin to host,  2 NUMA nodes, vCPU pinning 0#0_1#1_2#2_3#3, leave auto-pinning policy as "Don't change". Run the VM.
2. Open Edit dialog for this running VM. Don't change anything. Click OK.


Actual results:The VM is marked with next configuration changes mark.

Expected results:If nothing was changed on the VM it must not be marked with next configuration changes.


Additional info:

Comment 1 Polina 2021-06-03 09:40:50 UTC
verified on ovirt-engine-4.4.7-0.23.el8ev.noarch

Comment 2 Sandro Bonazzola 2021-07-06 07:28:27 UTC
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.7 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.