RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

[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.

Created attachment 592683 [details]
vdsm log

Created attachment 592684 [details]
engine log

Moving to vdsm, vdsm should provide appropriate error message

(In reply to comment #3)
> Moving to vdsm, vdsm should provide appropriate error message

ack

http://gerrit.ovirt.org/#/c/6083/

set on verify on behalf of gickowic

only with single host, 2 domains.

vdsm-4.9.6-26.0.el6_3.x86_64

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