Bug 1033123

Summary:	LVM logical volumes on FC SDs are activated automatically after hypervisor reboot
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	rhev-integ
Component:	vdsm	Assignee:	Nir Soffer <nsoffer>
Status:	CLOSED ERRATA	QA Contact:	Aharon Canan <acanan>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.2.0	CC:	abaron, acanan, amureini, bazulay, cboyle, fsimonce, hateya, iheim, lpeer, lyarwood, nsoffer, pzhukov, rhodain, scohen, sputhenp, yeylon, ykaplan
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	3.2.5
Hardware:	x86_64
OS:	Linux
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	When a hypervisor was rebooted all LVs which were part of a FC storage domain were automatically activated. This was cause some issues on occasion, as logical volumes should by activated only on request of the engine if needed (VM start), and deactivate immediately when the LVs are not needed (VM stop). This happened because when using FC storage, physical volumes are connected during boot, and vdsm. Logical volumes are auto-activated by both /etc/rc.sysinit and /etc/init.d/netfs startup scripts. These logical volumes did not pick changes done by the SPM on the storage, which could eventually lead to data corruption when a vm is trying to write to the logical volume with stale meta data. The fix checks all vdsm logical volumes during lvm bootstrap and deactivates them if possible. Special logical volumes are refreshed, since they are accessed early when connecting to storage pool, possibly before lvm bootstrap is done. Open logical volumes are skipped because it is assumed that they use correct meta data when opened.	Story Points:	---
Clone Of:	1009812	Environment:
Last Closed:	2013-12-18 13:58:49 UTC	Type:	---
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:	1009812
Bug Blocks:

Comment 2 Aharon Canan 2013-11-28 10:19:01 UTC


verified using sf22

1. one host setup with FC storage domain
2. create VM with few disks
3, run VM and power it off
4. enter host to maintenance
5. restart host
6. all LV are not active (VM is still down)
7. add new disk - disk is not active
8, start VM - all disks are active.

Comment 4 errata-xmlrpc 2013-12-18 13:58:49 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