Bug 728365
| Summary: | any change to lvm.conf results in an invalid HA configuration | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Corey Marthaler <cmarthal> | ||||||
| Component: | resource-agents | Assignee: | Jonathan Earl Brassow <jbrassow> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 6.1 | CC: | agk, ccaulfie, cfeist, cluster-maint, dwysocha, heinzm, jbrassow, lhh, mbroz, mjuricek, prajnoha, prockai, rpeterso, slevine, syeghiay, teigland, thornber, zkabelac | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | resource-agents-3.9.2-14.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
For HA LVM to work properly, the initrd which the system uses during the boot process must be in-sync with lvm.conf. A warning and an error are produced if the initrd is younger than lvm.conf. This has been reduced to simply an error message due to possible issues it can cause once the HA setup is operating.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 773372 (view as bug list) | Environment: | |||||||
| Last Closed: | 2013-02-21 07:51:47 UTC | Type: | --- | ||||||
| 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: | 773372, 817060, 818063 | ||||||||
| Attachments: |
|
||||||||
|
Description
Corey Marthaler
2011-08-04 20:25:31 UTC
Do we know yet whether we need to clone this as a documentation bug for RHEL 6.2 (and 5.8)? Since RHEL 6.2 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. I'm going to make it so that the script warns the user, but doesn't error out. It is important that the initrd be updated with lvm.conf changes. However, making HA LVM fail because of it is overkill. *** Bug 817060 has been marked as a duplicate of this bug. *** Created attachment 580844 [details]
3 Patches to fix the problem
Here is a set of three patches that must be added to the upstream 'resource-agents' repository and make their way into the corresponding resource-agents package for this bug.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
For HA LVM to work properly, the initrd which the system uses during the boot process must be in-sync with lvm.conf. A warning and an error are produced if the initrd is younger than lvm.conf. This has been reduced to simply an error message due to possible issues it can cause once the HA setup is operating.
Adding QA ack for 6.4. Devel will need to provide unit testing results however before this bug can be ultimately verified by QA. Fix committed upstream in branch RHEL6 as follows:
commit 33b5abfb99e0de71fea3d7a39901dea576129458
Author: Jonathan Brassow <jbrassow>
Date: Fri Oct 5 14:07:06 2012 -0500
LVM Agents: Warn instead of fail if initrd is newer than lvm.conf
There are many reasons why a user may change the lvm.conf file. They might
change filters or default segment types, etc. Making the HA LVM scripts
error our every time the lvm.conf file is newer than the initrd, can cause
serious problems. For example, if a service is running and lvm.conf is
changed, a subsequent fail-over would not work because the HA LVM script
would abort on this condition.
Instead of making things potentially worse, we have the scripts warn the
user (rather than failing) whenever this condition is hit. That way,
the user isn't suddenly surprised by things not working.
Signed-off-by: Jonathan Brassow <jbrassow>
Comment on attachment 580844 [details]
3 Patches to fix the problem
The patches are no longer necessary as they are now upstream
Created attachment 625132 [details]
upstream committed patch for 728365
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-0288.html |