Bug 1925079

Summary: SATA disk interface is missing when creating a new VM
Product: [oVirt] ovirt-engine Reporter: Tamir <tamir>
Component: Frontend.WebAdminAssignee: Shmuel Melamud <smelamud>
Status: CLOSED CURRENTRELEASE QA Contact: Tamir <tamir>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.5.3CC: ahadas, bugs, ljelinko
Target Milestone: ovirt-4.4.7Flags: pm-rhel: ovirt-4.4+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.7.5 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-06 07:28:05 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
Image of all the interfaces listed in the dropdown none

Description Tamir 2021-02-04 11:20:43 UTC
Created attachment 1755043 [details]
Image of all the interfaces listed in the dropdown

Description of problem:
When creating a new VM and in the new VM modal creating a new disk, the "New Virtual Disk" modal doesn't contain the SATA interface in the "Interfaces" dropdown.  

Version-Release number of selected component (if applicable):
  - Engine instance with RHV 4.4.5-3 (ovirt-engine-4.4.5.3-0.14.el8ev) and RHEL 8.3 installed.
  - 3 hosts with RHV 4.4.5-3 and RHEL 8.3, 3 hosts with vdsm-4.40.50.3-1.el8ev

How reproducible:
100%

Steps to Reproduce:

In Admin Portal:

1. Create a 4.5 data center and a 4.5 cluster.
2. Install the host and create a new NFS storage domain.
3. Open the "New Virtual Machine" modal.
4. Write a name for the new VM.
5. Open the "New Virtual Disk" modal using the "Create" button under "Instance Images".
6. Open the "Interface" dropdown.
7. Check that "SATA" interface is one of the options. 

Actual results:
1. The 4.5 data center and the 4.5 cluster were created.
2. The host was installed and the NFS storage domain was created.
3. The "New Virtual Machine" modal was opened.
4. The new VM name was chosen.
5. The "New Virtual Disk" modal was opened.
6. The "Interface" dropdown was opened.
7. The "SATA" interface wasn't listed in the dropdown.


Expected results:
1-6 steps are as expected.
7. The "SATA" interface should be listed in the dropdown.

Additional info:
Currently as a workaround you can create a VirtIO disk and after it's creation you can change the disk interface to "SATA".

Comment 1 Arik 2021-04-08 11:24:09 UTC
Lucia, is it solved by your changes to the bios type maybe?

Comment 2 Lucia Jelinkova 2021-04-13 09:29:52 UTC
Yes, this will be solved by the new bios type changes.

Comment 3 Shmuel Melamud 2021-06-30 23:28:27 UTC
I confirm that SATA interface is now appearing in the list of interfaces after performing the reproduction steps.

Comment 4 Tamir 2021-07-01 07:53:40 UTC
Verified on RHV 4.4.7-5. All looks good to me.

Env:
  - Engine instance with RHV 4.4.7-5 (ovirt-engine-4.4.7.5-0.9.el8ev) and RHEL 8.4 installed.
  - 3 hosts with RHV 4.4.7-5 and RHEL 8.4, vdsm-4.40.70.5-1.el8ev

In Admin Portal:

1. Create a 4.5 data center and a 4.5 cluster.
2. Install the host and create a new NFS storage domain.
3. Open the "New Virtual Machine" modal.
4. Write a name for the new VM.
5. Open the "New Virtual Disk" modal using the "Create" button under "Instance Images".
6. Open the "Interface" dropdown.
7. Check that "SATA" interface is one of the options.
8. Create a new SATA disk.
9. Check the SATA disk exists.

Actual results as expected:
1. The 4.5 data center and the 4.5 cluster were created.
2. The host was installed and the NFS storage domain was created.
3. The modal has opened.
4. I Written a name for the VM.
5. The "New Virtual Disk" modal has opened.
6. The dropdown has opened.
7. The SATA interface appears as one of the options.
8. I created a new SATA disk.
9. The new SATA disk appears in the VM modal/and after VM creation in it's Disks list.

Comment 5 Sandro Bonazzola 2021-07-06 07:28:05 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.