3.1 - [Storage] engine should do reconstruct master to take care the situation when the metadata is corrupted and vdsm sends to engine "general" exception.
In an earlier version of Red Hat Enterprise Virtualization, sometimes metadata on a host became corrupted and VDSM sent the engine a "general" exception. The pool SPM ID value was incorrectly set to "None". When this happened, VDSM threw a general exception saying "MetaDataParamError: Meta Data parameter invalid: ('Version or spm id invalid')".
Now when this happens, the engine reconstructs the master. This repairs the metadata.
[Storage] Engine should do reconstruct master to take care the situation when the metadata is corrupted and vdsm sends to engine "general" exception.
We have situation when metadata file on a host got corrupted. Pool SPM ID value is 'None' (which is wrong) in metadata file.
In this case vdsm troughs general exception saying MetaDataParamError: Meta Data parameter invalid: ('Version or spm id invalid',).In such a case engine should do reconstruct master in order to fix the metadata.
log files are attached.
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/RHSA-2012-1508.html
[Storage] Engine should do reconstruct master to take care the situation when the metadata is corrupted and vdsm sends to engine "general" exception. We have situation when metadata file on a host got corrupted. Pool SPM ID value is 'None' (which is wrong) in metadata file. In this case vdsm troughs general exception saying MetaDataParamError: Meta Data parameter invalid: ('Version or spm id invalid',).In such a case engine should do reconstruct master in order to fix the metadata. log files are attached.