Bug 1025467
| Summary: | SD is partially accessible after extending. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Chris Pelland <cpelland> |
| Component: | vdsm | Assignee: | Sergey Gotliv <sgotliv> |
| Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.2.0 | CC: | abaron, amureini, bazulay, cboyle, cww, hateya, iheim, jentrena, lpeer, lyarwood, michele, mkalinin, nsoffer, pablo.iranzo, pep, pzhukov, scohen, sgotliv, sreber, tnisan, yeylon |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | 3.2.5 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | storage | ||
| 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.
|
Story Points: | --- |
| Clone Of: | 1022976 | Environment: | |
| Last Closed: | 2013-12-18 13:58:15 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: | |||
| Bug Depends On: | 1022976, 1023206 | ||
| Bug Blocks: | |||
|
Comment 4
Aharon Canan
2013-11-28 13:56:43 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 |