Bug 1841183 - Exported disk on SD has no name in import subtab
Summary: Exported disk on SD has no name in import subtab
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.2
: ---
Assignee: Ahmad Khiet
QA Contact: Evelina Shames
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-28 15:24 UTC by Petr Matyáš
Modified: 2021-05-13 06:20 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-22 10:22:15 UTC
oVirt Team: Storage
Embargoed:
pm-rhel: ovirt-4.4+
mtessun: planning_ack+
sfishbai: testing_ack+

Attachments (Terms of Use)
engine log (1.49 MB, text/plain)
2020-05-28 15:24 UTC, Petr Matyáš 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 110255 0 master MERGED core: create disk description properly in CreateVolumeContainer 2020-10-13 11:02:38 UTC

Description Petr Matyáš 2020-05-28 15:24:59 UTC 
Created attachment 1693081 [details]
engine log

Description of problem:
When copying a disk to another SD, detaching that domain from current engine and attaching to a different one, I can not see any name for the disk.
After importing the disk it is named Registereddisk_date.

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

How reproducible:
always

Steps to Reproduce:
1. copy 2 disks from one storage domain to another (lets call the other one export for no reason at all)
2. detach the SD from first engine and attach to another one
3. go into Disk import subtab in the "export" storage domain

Actual results:
you can see 2 disks without names

Expected results:
the disks should have the same name as in the previous engine, otherwise you have no way to know which is which

Additional info:
The SD is attached as regular nfs data domain.
Comment 2 Lukas Svaty 2020-09-22 10:22:15 UTC 
CLOSING low QE severity 4.4.2 issuees with NEXT_RELESE. If you believe these bugs indeed require QE Verification feel free to reopen.
Note You need to log in before you can comment on or make changes to this bug.