Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1610459

Summary: [RFE] Resume VMs with Direct LUNs after being paused for I/O errors.
Product: [oVirt] ovirt-engine Reporter: Ryan <ryan>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED DEFERRED QA Contact: Avihai <aefrat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.4.5CC: bugs
Target Milestone: ---Keywords: FutureFeature
Target Release: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-01 14:47:22 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:

Description Ryan 2018-07-31 16:40:55 UTC 
Description of problem:

Discussed here: https://lists.ovirt.org/archives/list/users@ovirt.org/thread/NZKW5T4TJX2VP6M3DEEKNDQTUAZMRRSX/

Currently if you are using a Direct LUN and that VM gets paused due to I/O errors (SAN failover, etc) it will not get automatically resumed when the outage is cleared.

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


How reproducible:

Consistent/Easily

Steps to Reproduce:
1. Create a HA VM and attach a Direct LUN to it.
2. Create a storage outage for the Direct LUN. Wait for VM to pause.
3. Bring storage back online.

Actual results:

VM gets paused. Never resumes without manual intervention.

Expected results:

VM gets paused. When storage comes back online it should get resumed automatically.

Additional info:
Comment 1 Michal Skrivanek 2020-03-18 15:46:16 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 2 Michal Skrivanek 2020-03-18 15:51:07 UTC 
This bug didn't get any attention for a while, we didn't have the capacity to make any progress. If you deeply care about it or want to work on it please assign/target accordingly
Comment 3 Michal Skrivanek 2020-04-01 14:47:22 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.
Comment 4 Michal Skrivanek 2020-04-01 14:50:58 UTC 
ok, closing. Please reopen if still relevant/you want to work on it.