Bug 2080752 - VMs and VM pools that are created from a template are not set with the number of virtio-scsi multi-queue queues from the template
Summary: VMs and VM pools that are created from a template are not set with the number...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.5.0.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ovirt-4.5.1
: ---
Assignee: Shmuel Melamud
QA Contact: Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-01 15:22 UTC by Tamir
Modified: 2022-06-23 05:54 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-4.5.1
Clone Of:
Environment:
Last Closed: 2022-06-23 05:54:58 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt ovirt-engine pull 369 0 None open webadmin: Fill models with VirtioScsiMultiQueues 2022-05-11 22:22:57 UTC
Red Hat Issue Tracker RHV-45896 0 None None None 2022-05-01 15:29:34 UTC

Description Tamir 2022-05-01 15:22:41 UTC
Description of problem:

After the creation of a template with VirtIO-SCSI Multi Queues set to Custom and any number of queues, in our case 3, in the creation of a VM/ a VM pool from that template, the VM, the VM pool, and the created VM pool VMs are configured with VirtIO-SCSI Multi Queues set to Disabled.

Version-Release number of selected component (if applicable):
    - Engine instance with RHV 4.5.0-8 (ovirt-engine-4.5.0.5-0.7.el8ev) and RHEL 8.6 installed.
    - 3 hosts with RHV 4.5.0-8 and RHEL 8.6 and with vdsm-4.50.0.13-1.el8ev.

How reproducible:
100%

Steps to Reproduce:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create an RHEL VM with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. Create a template from the VM.
5. Create a VM pool from the latest version of the template with size: 1 and a regular VM.
6. Check for every created VM that VirtIO-SCSI Multi Queues set to Custom, and the number of queues is set to 3.

Actual results:
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed and the NFS storage domain was created.
3. The VM was created with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. The template was created.
5. The VM pool and 2 VM were created (1 from the VM pool).
6. The newly created VMs are set with VirtIO-SCSI Multi Queues set to Disabled.

Expected results:
Steps 1-5 results are as expected. 
In step 6, the created VMs should have VirtIO-SCSI Multi Queues set to Custom, and the number of queues should be set to 3.

Comment 1 Tamir 2022-06-07 14:47:43 UTC
Verified on RHV 4.5.1-1.

Env:
    - Engine instance with RHV 4.5.1-1 (ovirt-engine-4.5.1-0.62.el8ev) and RHEL 8.6 installed.
    - 2 hosts with RHV 4.5.1-1 and RHEL 8.6 and with vdsm-4.50.1.1-1.el8ev.

Steps:

In Admin Portal:
1. Create a 4.7 data center and a 4.7 cluster.
2. Install the hosts and create a new NFS storage domain.
3. Create an RHEL VM with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. Create a template from the VM.
5. Create a VM pool from the latest version of the template with size: 1 and a regular VM.
6. Check for every created VM that VirtIO-SCSI Multi Queues set to Custom, and the number of queues is set to 3.

Results (As Expected):
1. The 4.7 data center and the 4.7 cluster were created.
2. The hosts were installed and the NFS storage domain was created.
3. The VM was created with VirtIO-SCSI Multi Queues set to Custom and 3 queues.
4. The template was created.
5. The VM pool and 2 VM were created (1 from the VM pool).
6. The VMs are created with VirtIO-SCSI Multi Queues set to Custom and 3 queues.

Comment 2 Sandro Bonazzola 2022-06-23 05:54:58 UTC
This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 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.


Note You need to log in before you can comment on or make changes to this bug.