Bug 1603195

Summary: On 'Copy Disk' popup, the source storage domain appears twice, so the 'Disk Profile' column was pushed to another line
Product: [oVirt] ovirt-engine Reporter: shani <sleviim>
Component: BLL.StorageAssignee: shani <sleviim>
Status: CLOSED CURRENTRELEASE QA Contact: Elad <ebenahar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: bugs, ratamir
Target Milestone: ovirt-4.3.0Flags: rule-engine: ovirt-4.3+
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-4.3.0_alpha Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 07:48:10 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
the table on 'copy disks' popup none

Description shani 2018-07-19 12:26:36 UTC
Created attachment 1460025 [details]
the table on 'copy disks' popup

Description of problem:
On the 'Copy Disk' popup, the disk profile was moved to another line on the table, since the source storage domain's value appears twice (once as a label and once as a list-box) on two different columns, so the other columns' values were moves 1 place to the right.
(see attached screenshot)

Version-Release number of selected component (if applicable):
master-7b828a9092d

How reproducible:
100%

Steps to Reproduce:
1. Select a disk on Storage > Disks tab
2. Press 'copy'
3.

Actual results:
The source storage appears twice and the disk profile appears on a new line.

Expected results:
The source storage should appear only once and the disk profile appears on its appropriate column.

Additional info:
Screenshot

Comment 1 Elad 2018-08-15 15:25:22 UTC
In copy disk prompt, the source domain appears once as should be, hence the disk profile is in place.


4.3.0-0.0.master.20180814113734.gitad81cd3.el7

Comment 2 Sandro Bonazzola 2018-11-02 14:35:15 UTC
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018.

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

Comment 3 Sandro Bonazzola 2018-11-02 15:05:33 UTC
Closed by mistake, moving back to qa -> verified

Comment 4 Sandro Bonazzola 2019-02-13 07:48:10 UTC
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019.

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