Bug 682793

Summary: Test mode switch is ignored with cluster locking in vgchange
Product: Red Hat Enterprise Linux 6 Reporter: Milan Broz <mbroz>
Component: lvm2Assignee: LVM and device-mapper development team <lvm-team>
Status: CLOSED UPSTREAM QA Contact: Corey Marthaler <cmarthal>
Severity: low Docs Contact:
Priority: low    
Version: 6.3CC: agk, coughlan, dwysocha, heinzm, jbrassow, mcsontos, prajnoha, prockai, pvrabec, thornber, zkabelac
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-05 14:49:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 756082    

Description Milan Broz 2011-03-07 15:45:29 UTC 
Description of problem:

# lvs
  LV      VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  lv      vg_test  -wi--- 100.00g                                      
[root@bar-01 ~]# vgchange -t -a y vg_test ; echo $?
  Test mode: Metadata will NOT be updated and volumes will not be (de)activated.
  1 logical volume(s) in volume group "vg_test" now active
0
[root@bar-01 ~]# lvs
  LV      VG       Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  lv      vg_test  -wi-a- 100.00g                                      


Version-Release number of selected component (if applicable):
lvm2-2.02.82-1.el6
Comment 1 RHEL Program Management 2011-04-04 02:09:48 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 2 Milan Broz 2011-05-30 12:48:29 UTC 
This is generic problem with test flag & cluster.

It must be distributed across the cluster to make it work.
I think because this is not critical problem, we can move it to 6.3, precisely fix it after clvmd locking protocol change.

(Adding another bits in current protocol is almost impostible without ugly hacks today...)
Comment 3 Alasdair Kergon 2011-05-30 13:18:27 UTC 
Indeed, test_mode() is called from the local activation code and so must be propagated around the cluster.  Not a regression - the code has always behaved like this - and clearly not very important because nobody has noticed it until now!
Comment 5 RHEL Program Management 2012-07-10 05:57:50 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 6 RHEL Program Management 2012-07-10 23:56:26 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 7 Marian Csontos 2012-11-13 11:54:18 UTC 
If we suppose the LVM metadata are consistent across the cluster (which is a sane assumption if not an axiom) is it necessary to propagate '--test' flag to other nodes at all?
Comment 8 Alasdair Kergon 2012-12-05 14:45:24 UTC 
upstream 2.02.86 released 2011/07/08 WHATS_NEW:
  Propagate test mode to clvmd to skip activation and changes to held locks.
Comment 9 Alasdair Kergon 2012-12-05 14:49:32 UTC 
Seems to have been fixed outside this bugzilla.  If any further problems are found with --test in clusters, please open new bugs.