Bug 927594
| Summary: | webadmin portal new storage domain window selectable LUNs don't match the reported "In Use" status | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Julio Entrena Perez <jentrena> | ||||||||
| Component: | ovirt-engine-webadmin-portal | Assignee: | Ayal Baron <abaron> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Haim <hateya> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.1.3 | CC: | acathrow, amureini, dyasny, ecohen, hateya, iheim, jentrena, pep, Rhev-m-bugs, yeylon, ykaul | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.3.0 | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | storage | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-03-26 22:00:04 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: |
|
||||||||||
Aditionally "Used" LUNs are selectable. Although doing so triggers the warning message below it's still confusing for the end user. This operation might be unrecoverable and destructive! The following LUNs are already in use: - 1IET_00010003 (Used by VG: CiS9nz-g5tT-cCZZ-QB0I-iEEy-Yt2u-JXxq3s) Approve operation [ ] please attach full engine and vdsm logs. also, provide the following information from the hypervisor: - lsblk - pvs -a I don't think its related to webadmin component (at best, it will be backend). (In reply to comment #2) > please attach full engine and vdsm logs. Attached. > also, provide the following information from the hypervisor: > > - lsblk # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 232.9G 0 disk ├─sda1 8:1 0 200M 0 part /boot ├─sda2 8:2 0 1000M 0 part [SWAP] └─sda3 8:3 0 231.7G 0 part └─myvg-rootvol (dm-0) 253:0 0 231.7G 0 lvm / sdc 8:32 0 183.8G 0 disk └─1IET_00010002 (dm-3) 253:3 0 183.8G 0 mpath ├─30316a18--b5a7--4762--9440--893b325ec602-metadata (dm-10) 253:10 0 512M 0 lvm ├─30316a18--b5a7--4762--9440--893b325ec602-ids (dm-11) 253:11 0 128M 0 lvm ├─30316a18--b5a7--4762--9440--893b325ec602-leases (dm-12) 253:12 0 2G 0 lvm ├─30316a18--b5a7--4762--9440--893b325ec602-inbox (dm-13) 253:13 0 128M 0 lvm ├─30316a18--b5a7--4762--9440--893b325ec602-outbox (dm-14) 253:14 0 128M 0 lvm └─30316a18--b5a7--4762--9440--893b325ec602-master (dm-15) 253:15 0 1G 0 lvm /rhev/data-center/mnt/block sdd 8:48 0 183.8G 0 disk └─1IET_00010003 (dm-2) 253:2 0 183.8G 0 mpath ├─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-metadata (dm-4) 253:4 0 512M 0 lvm ├─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-ids (dm-5) 253:5 0 128M 0 lvm ├─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-leases (dm-6) 253:6 0 2G 0 lvm ├─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-inbox (dm-7) 253:7 0 128M 0 lvm ├─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-outbox (dm-8) 253:8 0 128M 0 lvm └─b5a89606--302b--42a2--beb2--1aea5bc4ffa2-master (dm-9) 253:9 0 1G 0 lvm sdb 8:16 0 10G 0 disk └─1IET_00010001 (dm-1) 253:1 0 10G 0 mpath > - pvs -a # pvs -a | grep -v ram PV VG Fmt Attr PSize PFree /dev/30316a18-b5a7-4762-9440-893b325ec602/ids --- 0 0 /dev/30316a18-b5a7-4762-9440-893b325ec602/inbox --- 0 0 /dev/30316a18-b5a7-4762-9440-893b325ec602/leases --- 0 0 /dev/30316a18-b5a7-4762-9440-893b325ec602/master --- 0 0 /dev/30316a18-b5a7-4762-9440-893b325ec602/metadata --- 0 0 /dev/30316a18-b5a7-4762-9440-893b325ec602/outbox --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/ids --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/inbox --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/leases --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/master --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/metadata --- 0 0 /dev/b5a89606-302b-42a2-beb2-1aea5bc4ffa2/outbox --- 0 0 /dev/mapper/1IET_00010001 --- 0 0 /dev/mapper/1IET_00010002 30316a18-b5a7-4762-9440-893b325ec602 lvm2 a-- 183.50g 110.62g /dev/mapper/1IET_00010003 b5a89606-302b-42a2-beb2-1aea5bc4ffa2 lvm2 a-- 183.50g 179.62g /dev/root --- 0 0 /dev/sda1 --- 0 0 /dev/sda2 --- 0 0 /dev/sda3 myvg lvm2 a-- 231.69g 0 > > I don't think its related to webadmin component (at best, it will be > backend). Created attachment 716438 [details]
engine.log
Created attachment 716439 [details]
vdsm.log
the following block devices are already in use an has storage domain metadata on it, hence, you cannot use it:
sdc 8:32 0 183.8G 0 disk
`-1IET_00010002 (dm-3) 253:3 0 183.8G 0 mpath
|-30316a18--b5a7--4762--9440--893b325ec602-metadata (dm-10) 253:10 0 512M 0 lvm
|-30316a18--b5a7--4762--9440--893b325ec602-ids (dm-11) 253:11 0 128M 0 lvm
|-30316a18--b5a7--4762--9440--893b325ec602-leases (dm-12) 253:12 0 2G 0 lvm
|-30316a18--b5a7--4762--9440--893b325ec602-inbox (dm-13) 253:13 0 128M 0 lvm
|-30316a18--b5a7--4762--9440--893b325ec602-outbox (dm-14) 253:14 0 128M 0 lvm
`-30316a18--b5a7--4762--9440--893b325ec602-master (dm-15) 253:15 0 1G 0 lvm /rhev/data-center/mnt/blockSD/30316a18-b5a7-4762-9440-893b325ec602/master
sdd 8:48 0 183.8G 0 disk
`-1IET_00010003 (dm-2) 253:2 0 183.8G 0 mpath
|-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-metadata (dm-4) 253:4 0 512M 0 lvm
|-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-ids (dm-5) 253:5 0 128M 0 lvm
|-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-leases (dm-6) 253:6 0 2G 0 lvm
|-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-inbox (dm-7) 253:7 0 128M 0 lvm
|-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-outbox (dm-8) 253:8 0 128M 0 lvm
`-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-master (dm-9) 253:9 0 1G 0 lvm
as for 1IET_00010001, from some reason it still in your data-base, hence engine prevents you from using it, need to understand why.
btw - the reason engine not allows you to use 1IET_00010002 comes from the fact its a part of your active storage domain.
I don't think there is a bug here, its all by design.
as for leftover in the data-base [1], need to look into that, but its not related to bug report.
[1]
engine=# SELECT * from luns;
physical_volume_id | lun_id | volume_group_id | serial | lun_mapping | vendor_id | product_id | device_size
----------------------------------------+---------------+----------------------------------------+-------------------+-------------+-----------+--------------+-------------
ydbSri-WZkq-jfWF-wi39-FaT4-xmpS-SGfGyw | 1IET_00010001 | kIleSn-FyLx-TDs0-GplM-kHAo-ZzTv-y9dcTi | SIET_VIRTUAL-DISK | 1 | IET | VIRTUAL-DISK | 183
93UThW-JVWC-PlOx-LNhC-fQuT-id2B-U4IFZm | 1IET_00010002 | CiS9nz-g5tT-cCZZ-QB0I-iEEy-Yt2u-JXxq3s | SIET_VIRTUAL-DISK | 2 | IET | VIRTUAL-DISK | 183
(In reply to comment #7) > the following block devices are already in use an has storage domain > metadata on it, hence, you cannot use it: > > sdc 8:32 0 > 183.8G 0 disk > `-1IET_00010002 (dm-3) 253:3 0 > 183.8G 0 mpath > |-30316a18--b5a7--4762--9440--893b325ec602-metadata (dm-10) 253:10 0 > 512M 0 lvm > |-30316a18--b5a7--4762--9440--893b325ec602-ids (dm-11) 253:11 0 > 128M 0 lvm > |-30316a18--b5a7--4762--9440--893b325ec602-leases (dm-12) 253:12 0 > 2G 0 lvm > |-30316a18--b5a7--4762--9440--893b325ec602-inbox (dm-13) 253:13 0 > 128M 0 lvm > |-30316a18--b5a7--4762--9440--893b325ec602-outbox (dm-14) 253:14 0 > 128M 0 lvm > `-30316a18--b5a7--4762--9440--893b325ec602-master (dm-15) 253:15 0 > 1G 0 lvm > /rhev/data-center/mnt/blockSD/30316a18-b5a7-4762-9440-893b325ec602/master > sdd 8:48 0 > 183.8G 0 disk > `-1IET_00010003 (dm-2) 253:2 0 > 183.8G 0 mpath > |-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-metadata (dm-4) 253:4 0 > 512M 0 lvm > |-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-ids (dm-5) 253:5 0 > 128M 0 lvm > |-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-leases (dm-6) 253:6 0 > 2G 0 lvm > |-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-inbox (dm-7) 253:7 0 > 128M 0 lvm > |-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-outbox (dm-8) 253:8 0 > 128M 0 lvm > `-b5a89606--302b--42a2--beb2--1aea5bc4ffa2-master (dm-9) 253:9 0 > 1G 0 lvm > > > as for 1IET_00010001, from some reason it still in your data-base, hence > engine prevents you from using it, need to understand why. > > btw - the reason engine not allows you to use 1IET_00010002 comes from the > fact its a part of your active storage domain. > > I don't think there is a bug here, its all by design. Well, 1IET_00010003 is "Used" but selectable. 1IET_00010002 is "Used" but not selectable. Additionally 1IET_00010001 is "Free" but not selectable. Sorry but I'm struggling to understand how this is expected behaviour. > > as for leftover in the data-base [1], need to look into that, but its not > related to bug report. > > [1] > > engine=# SELECT * from luns; > physical_volume_id | lun_id | > volume_group_id | serial | lun_mapping | vendor_id | > product_id | device_size > ----------------------------------------+---------------+-------------------- > --------------------+-------------------+-------------+-----------+---------- > ----+------------- > ydbSri-WZkq-jfWF-wi39-FaT4-xmpS-SGfGyw | 1IET_00010001 | > kIleSn-FyLx-TDs0-GplM-kHAo-ZzTv-y9dcTi | SIET_VIRTUAL-DISK | 1 | > IET | VIRTUAL-DISK | 183 > 93UThW-JVWC-PlOx-LNhC-fQuT-id2B-U4IFZm | 1IET_00010002 | > CiS9nz-g5tT-cCZZ-QB0I-iEEy-Yt2u-JXxq3s | SIET_VIRTUAL-DISK | 2 | > IET | VIRTUAL-DISK | 183 *** This bug has been marked as a duplicate of bug 921544 *** |
Created attachment 716399 [details] Free LUN is grayed out and can not be selected. Description of problem: After presenting a new LUN to RHEV, new storage domain LUN selection window shows LUNs reported as free but "grayed out" (non selectable). Version-Release number of selected component (if applicable): rhevm-webadmin-portal-3.1.0-50.el6ev.noarch How reproducible: Always. Steps to Reproduce: 1. Present a new LUN to RHEV. 2. In WebAdmin portal, go to "Storage" tab and select "New Domain". 3. Actual results: Free LUN is grayed out and non selectable. Expected results: Free LUN is not grayed out and can be selected. Additional info: See attached screenshot.