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.

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.

I'm closing this one as duplicate of Bug #1007074.  This BZ added few more checks when metadata could be swapped.

It relates to this BZ as well - since if the thin-pool would be inactive,
not activation for swapped thin-pool is made.

However if someone tries to activate thin-pool with incorrect metadata,
he needs to deal with consequences - which currently may enforce user
to manually remove devices from dm table.

So if the 'newMDA' doesn't have valid metadata, the user will need to swap back valid metadata for the snapper_thinp/POOL device - or has to manually  remove entries from dm table and  vgcfgrestore metadata without any appearance of the POOL in them (thin data & metadata and thin volumes removed).

Swapping is only meant to be used for manual recovery of damaged pool (which may eventually be stacked over raids).

*** This bug has been marked as a duplicate of bug 1007074 ***