Bug 1570383

Summary: [PPC] Webadmin doesn't expose sPAPR VSCSI disk interface in disk creation prompt that is initiated from within VM creation prompt
Product: [oVirt] ovirt-engine Reporter: Elad <ebenahar>
Component: Frontend.WebAdminAssignee: shani <sleviim>
Status: CLOSED CURRENTRELEASE QA Contact: Shir Fishbain <sfishbai>
Severity: medium Docs Contact:
Priority: low    
Version: 4.2.3.2CC: bugs, tnisan, ylavi
Target Milestone: ovirt-4.2.4Flags: rule-engine: ovirt-4.2+
ylavi: exception+
Target Release: ---   
Hardware: ppc64le   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.2.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-26 08:44:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
video capture none

Description Elad 2018-04-22 12:46:01 UTC
Created attachment 1425325 [details]
video capture

Description of problem:
See attached video capture

Version-Release number of selected component (if applicable):
rhvm-4.2.3.2-0.1.el7.noarch
vdsm-4.20.26-1.el7ev.ppc64le

How reproducible:
Always

Steps to Reproduce:
PPC env:
1. Open VM creation prompt, open disk creation prompt from it


Actual results:
No sPAPR VSCSI for the newly about to be created disk

Workaround:
Create the VM without a disk attached and in its new attach disk prompt, sPAPR VSCSI will exist

Expected results:
sPAPR VSCSI disk interface should appear while opening new disk creation prompt from within VM creation prompt

Additional info:

Comment 1 Shir Fishbain 2018-05-27 14:45:40 UTC
Disk creation from add VM prompt now allows sPAPR VSCSI disk interface selection.

Used:
4.2.4

Comment 2 Sandro Bonazzola 2018-06-26 08:44:28 UTC
This bugzilla is included in oVirt 4.2.4 release, published on June 26th 2018.

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