vaibhav, can we get the relevant logs attached here please?
Created attachment 1406744 [details] engine.log
Created attachment 1406745 [details] VDSM.log From host hyperv04
Created attachment 1406759 [details] VDSM.log From host hyperv03
vaibhav, The customer reported that the disk eventually was unlocked. Can you get the latest logs (hosts+engine) after that the disk was unlocked from the customer to understand how the process eventually finished?
This bug is not marked as blocker and we enetered blocker only phase for 4.2.4. Please consider re-targeting to 4.2.5.
Created attachment 1458299 [details] engine and vdsm logs Added new logs after running scenario again with longer wait before blocking the access to the storage
Based on comment 18 and additional successful run moving to VERIFY
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops
Raz / Benny, This bug is on verified and 4.2.5 is out. Why is this bug still open? Who can confirm the correct status of it? Thank you!
(In reply to Marina from comment #22) > Raz / Benny, > > This bug is on verified and 4.2.5 is out. > Why is this bug still open? > Who can confirm the correct status of it? > > Thank you! I think it's a flag issue Tal, do you know?
I suspect that it's because it got in without a proper downstream clone, Anton, what can we do to rectify that?
https://access.redhat.com/errata/RHEA-2018:2319
sync2jira