Bug 1294071
Summary: | An attached disk appears power down but the VM is using it | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Sarvesh Pandit <sapandit> |
Component: | ovirt-engine | Assignee: | Amit Aviram <aaviram> |
Status: | CLOSED DUPLICATE | QA Contact: | Aharon Canan <acanan> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.5.4 | CC: | aaviram, acanan, ahino, amureini, ecohen, gklein, kgoldbla, lsurette, rbalakri, Rhev-m-bugs, sapandit, tnisan, yeylon |
Target Milestone: | ovirt-3.6.5 | ||
Target Release: | 4.0.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | storage | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-01-24 13:12:02 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
Sarvesh Pandit
2015-12-24 12:13:10 UTC
Given the timeline it will not make it to 3.6.2, deferring to 3.6.5 until we get an answer in late January If the disk appears properly in the DB, doesn't a simple refresh of the GUI solve the issue? Hi Sarvesh, Can you elaborate the steps to reproduce this. Does this happen to all attached disks? Does this happen the moment you attach the disks and start the VM or after a specific event? (In reply to Allon Mureinik from comment #6) > If the disk appears properly in the DB, doesn't a simple refresh of the GUI > solve the issue? Sarvesh, can you answer this question please? This bug is probably a duplication of Bug 1044466 which was solved in 3.5.6. The bug is basically a faulted hotunplug at the host side, which reported a success back to the engine. in that case, the disk looks unplugged at the engine while it is actually still attached to the VM. Currently we will close the as duplicate- if the issue persists after upgrading to 3.5.6, please reopen. *** This bug has been marked as a duplicate of bug 1044466 *** |