Bug 1025467 - SD is partially accessible after extending.
Summary: SD is partially accessible after extending.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm
Version: 3.2.0
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
: 3.2.5
Assignee: Sergey Gotliv
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On: 1022976 1023206
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-31 18:50 UTC by Chris Pelland
Modified: 2018-12-09 17:15 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
After adding a new LUN to the existing storage domain (both FC and iSCIS BlockSD are affected) hosts (except SPM) became non-operational. VMs started to migrate but mostly failed. The domainMonitor thread might have been using stale lvm filters while running the vgs command after extending of the VG (added PV is missed in the filter set).Since LvmCache doesn't invalidate filters, the volume group is marked as partial and domainMonitor selftest fails (host goes to non-operational status). By design, the filter should be invalidated if cmd returns a nonzero code, but vgs returns zero even if the devices are filtered . The patch introduces a public method for filter invalidation and calls it from the getDevicesVisibility, because getDevicesVisibility is called on all DC hosts after adding a new device but before extendSD.
Clone Of: 1022976
Environment:
Last Closed: 2013-12-18 13:58:15 UTC
oVirt Team: Storage
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 522173 0 None None None Never
Red Hat Product Errata RHBA-2013:1832 0 normal SHIPPED_LIVE rhev 3.2.5 - vdsm bug fix update 2013-12-18 18:56:17 UTC
oVirt gerrit 20552 0 None None None Never

Comment 4 Aharon Canan 2013-11-28 13:56:43 UTC 

verified using sf22
Comment 7 errata-xmlrpc 2013-12-18 13:58:15 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1832.html
Note You need to log in before you can comment on or make changes to this bug.