Bug 820991
| Summary: | Adding an option to silently skip the clustered volume groups | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Federico Simoncelli <fsimonce> | |
| Component: | lvm2 | Assignee: | Alasdair Kergon <agk> | |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 6.3 | CC: | abaron, agk, cmarthal, cww, dwysocha, heinzm, jbrassow, jraju, jruemker, lnovich, mkalinin, msnitzer, nperic, pm-rhel, prajnoha, prockai, scohen, slevine, snagar, sputhenp, thornber, tlavigne, zkabelac | |
| Target Milestone: | rc | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | lvm2-2.02.100-5.el6 | Doc Type: | Bug Fix | |
| Doc Text: |
When there were visible clustered Volume Groups in the system, it was not possible to silently skip them with proper return error code while non-clustered locking type was used (the global/locking_type lvm.conf setting). To fix this bug, "--ignoreskippedcluster" option has been added for several LVM commands (pvs, vgs, lvs, pvdisplay, vgdisplay, lvdisplay, vgchange, and lvchange). With this option, the clustered Volume Groups are skipped correctly without any warning/error messages while the return error code also does not depend on these clustered Volume Groups.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 986463 1034764 (view as bug list) | Environment: | ||
| Last Closed: | 2013-11-21 23:16:34 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 820982, 951600, 986463, 1024911, 1034764, 1116944 | |||
|
Description
Federico Simoncelli
2012-05-11 13:53:51 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. 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. (bug #1005415) Also, during boot and the vgchange -ay call in rc.sysinit script, we get a "FAILURE" initscript status because of non-zero return value - this might be confusing (clustered VGs are activated later by another vgchange -ay call that is a part of the clvmd init script once we have cluster properly set up). The option to silently skip clustered volume groups on activation should be also used in this rc.sysinit script - once we have this option in, let's update initscripts as well. *** Bug 1005415 has been marked as a duplicate of this bug. *** I have a prototype patch that adds a new --ignoreskippedcluster option to pvs. This changes the 'Skipping' messages from stderr to verbose and means clustered VGs have no effect on the exit status if clustered locking is unavailable. [root@virt-008 ~]# pvs --config 'global {locking_type = 1}'
Skipping clustered volume group cluster
Skipping volume group cluster
Skipping clustered volume group cluster
Skipping volume group cluster
Skipping clustered volume group cluster
Skipping volume group cluster
Skipping clustered volume group cluster
Skipping volume group cluster
Skipping clustered volume group cluster
Skipping volume group cluster
Skipping clustered volume group cluster
Skipping volume group cluster
PV VG Fmt Attr PSize PFree
/dev/vda2 vg_virt008 lvm2 a-- 7.51g 0
[root@virt-008 ~]# echo $?
5
[root@virt-008 ~]# pvs --ignoreskippedcluster --config 'global {locking_type = 1}'
PV VG Fmt Attr PSize PFree
/dev/vda2 vg_virt008 lvm2 a-- 7.51g 0
[root@virt-008 ~]# echo $?
0
[root@virt-008 ~]#
Verified with: lvm2-2.02.100-6.el6.x86_64
Do we need another bug to pursue rc.sysinit changes? (In reply to John Ruemker from comment #32) > Do we need another bug to pursue rc.sysinit changes? Yes that would be a separate change for the "initscripts" component. 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-1704.html Bug for rc.sysinit change: https://bugzilla.redhat.com/show_bug.cgi?id=1034764 |