Comment # 21 on bug 997637 from Neil Rickert

An additional comment.  I'm not sure if this is relevant, but I will mention
it.

After a failed boot, I tried to manually access the LVM volumes.  And I ran
into this problem:

 ----
# vgchange -a y
  Request to list VGs in lvmetad gave response token_mismatch. Reason: lvmetad
cache is invalid due to a global_filter change or due to a running rescan
 ----
I did not see that on the alpha releases of 42.2.  I have seen that on both
Beta releases.

Additional information: the computer (system1 as identified in an earlier
comment) has two hard drives, with an encrypted LVM on each.  Install added
"crypttab" entries for both of those encrypted LVMs.  If I comment out the
crypttab entry that is not actually needed, then I do not run into error above.
 If I leave both entries uncomments (thus active), then I seem to always run
into that problem, which leaves no way of continuing.