Bug 1930282

Summary: vcpu pinning string for HP VM must be shown in UI(even if it must be disabled for editing)
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: Frontend.WebAdminAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.4.5CC: ahadas, bugs
Target Milestone: ovirt-4.4.6Flags: pm-rhel: ovirt-4.4+
Target Release: 4.4.6   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-05 05:36:03 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:

Description Polina 2021-02-18 16:09:40 UTC 
Description of problem:
Now when user configures the HP VM the auto pinning policy automatically switches to 'existing' and this sets the vcpu pinning to the host's vcpu pinning taking into account the cpu topology. 
but this is not shown to the user which is very confusing. If he creates a template from such VM he discovers vcpu pinning string on the created template as a surprise because he has no way to see it before on the VM. I think if it must be disabled for editing at least it must be shown in the field.

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

How reproducible:100%


Steps to Reproduce:
1.Configure VM with 4 cpus and some vcpu pinning string , like 0#0_1#1
2.Set HP Type , ok.


Actual results: The VM is set to existing policy as required. but the vcpu pinning string is shown as empty which is very confusing .

Expected results: even if it must be disabled for editing , it must be shown to the user.
Comment 1 Polina 2021-02-22 08:12:06 UTC 
For QE: please check an additional scenario: while changing the VM type from HP to Server, the vcpu pinning is removed from the VM (not only UI).
Comment 2 Polina 2021-04-13 09:00:35 UTC 
verified on ovirt-engine-4.4.6.3-0.8.el8ev.noarch
Comment 3 Sandro Bonazzola 2021-05-05 05:36:03 UTC 
This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021.

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