Description of problem: pvcreate test is failed with device not found (but it's actually there) and LUN is marked as used. Version-Release number of selected component (if applicable): vdsm-4.16.26-1.el7ev.x86_64 How reproducible: 100% (2/2 times in my env) Steps to Reproduce: 1. Create new DC 2. Install hypervisor 3. Create new iSCSI LUN 4. Try to add the LUN as SD Actual results: UI is failed with "LUN is already in use" Expected results: Successfully added LUN Additional info:
Created attachment 1069139 [details] vdsm log
# hexdump -C -n 20000 /dev/mapper/360014052a33b4595f4e4745a98b3fe8a 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00004e20
Created attachment 1069141 [details] engine log
Created attachment 1069143 [details] supervdsm log
Created attachment 1069183 [details] messages
Workaround is: 1) Approve operation 2) Storage domain addition FAILED! 3) Destroy SD 4) Add it again (approve operation again) Seems like the reason is multipath problem and separate bug should be created but the "LUN in use" is completely misleading wrong message.
Created attachment 1069269 [details] vdsm log
Pavel hi, It seems similar as [1] . If you run pvcreate with vvv for verbose ,and a partition is found , the following warning will be logged : 'Skipping: Partition table signature found' pvcreate -ffvvv /dev/mapper/3600a09803753795a64244531644f7846 ........ /dev/mapper/3600a09803753795a64244531644f7846: Skipping: Partition table signature found [none:(nil)] ........ Device /dev/mapper/3600a09803753795a64244531644f7846 not found (or ignored by filtering). Can you see if it is the same root cause ? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1215427#c4
(In reply to Fred Rolland from comment #8) > Pavel hi, > > It seems similar as [1] . > > If you run pvcreate with vvv for verbose ,and a partition is found , the > following warning will be logged : 'Skipping: Partition table signature > found' It's not the case here. I zero'ed the LUN before reproducing this second time.
(In reply to Pavel Zhukov from comment #6) > Workaround is: > 1) Approve operation > 2) Storage domain addition FAILED! > 3) Destroy SD > 4) Add it again (approve operation again) > > Seems like the reason is multipath problem and separate bug should be > created but the "LUN in use" is completely misleading wrong message. Hi, What do you mean that the reason is multipath problem ? Can you explain? Is this bug still relevant ? Thanks
(In reply to Fred Rolland from comment #10) > Hi, > > What do you mean that the reason is multipath problem ? Hi, Sorry but I don't remember what I meant more than one year ago... > Can you explain? Is this bug still relevant ? I'm not sure > > Thanks
Closing as there's not enough data here. Please re-open if more data / reproduction is available.