Hide Forgot
This bug has been copied from bug #669717 and has been proposed to be backported to 5.6 z-stream (EUS).
verified on vdsm22-4.5-63.12.el5_6. host no longer goes to non-operational. no longer get lvm scan errors.
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: On Red Hat Enterprise Linux 5, if the incorrect VDSM filter was used the volume group could not be found, which caused the host to become non-operational and issue lvm scan errors. The vdsm22-4.5-63.14.el5_6 package uses the correct VDSM filter and hosts no longer become non-operational or issue lvm scan errors.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -On Red Hat Enterprise Linux 5, if the incorrect VDSM filter was used the volume group could not be found, which caused the host to become non-operational and issue lvm scan errors. The vdsm22-4.5-63.14.el5_6 package uses the correct VDSM filter and hosts no longer become non-operational or issue lvm scan errors.+On Red Hat Enterprise Linux 5, if the incorrect VDSM filter was used the volume group could not be found, which caused the host to become non-operational and issue lvm scan errors. The current VDSM package uses the correct VDSM filter and hosts no longer become non-operational or issue lvm scan errors.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0319.html