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.
Bug 1069808 - "Request to update PV ... in lvmetad gave response token_mismatch" during net-install boot
Summary: "Request to update PV ... in lvmetad gave response token_mismatch" during net...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lvm2
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Rockai
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-25 17:00 UTC by Marian Csontos
Modified: 2021-09-03 12:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-28 13:39:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
journal after the installation is over (814.26 KB, text/plain)
2014-02-26 07:38 UTC, Marian Csontos 		no flags Details
lvmdump (1.66 MB, application/x-gzip)
2014-02-27 11:25 UTC, Marian Csontos 		no flags Details
View All

Description Marian Csontos 2014-02-25 17:00:10 UTC 
Description of problem:

During testing more complex LVM layouts I am seeing messages like these on console:

    Feb 25 15:39:39 localhost pvscan[1138]: Request to update PV WC8isV-W2Fl-XluT-9YdW-OdOv-bmv1-jRJJg7 in lvmetad gave response token_mismatch. Reason: token        mismatch
    Feb 25 15:39:39 localhost pvscan[1138]: Update of lvmetad failed. This is a serious problem.
    Feb 25 15:39:39 localhost pvscan[1138]: It is strongly recommended that you restart lvmetad immediately.
    Feb 25 15:39:39 localhost systemd[1]: lvm2-pvscan@252:129.service: main process exited, code=exited, status=5/NOTINSSTALLED
    Feb 25 15:39:39 localhost systemd[1]: Failed to start LVM2 PV scan on device 252:129.
    Feb 25 15:39:39 localhost systemd[1]: Unit lvm2-pvscan@252:129.service entered failed state.

I have 8 PVs with MDAs and this happens for 6 of them, remaining 2 usually run fine.

This does not happen after the system is installed.

Version-Release number of selected component (if applicable):
anaconda 19.31.60-1
lvm2-2.02.105-4.el7
compose RHEL-7.0-20140220.2

How reproducible:
100% (with given layout)

Steps to Reproduce:
1. boot net-boot image in VM with given layout

Actual results:

Scary messages about lvmetad asking for immediate restart of the service:

    Feb 25 15:39:39 localhost pvscan[1138]: Update of lvmetad failed. This is a serious problem.
    Feb 25 15:39:39 localhost pvscan[1138]: It is strongly recommended that you restart lvmetad immediately.

Expected results:

Clean boot.

Additional info:
Comment 2 Marian Csontos 2014-02-25 17:05:15 UTC 
This may be related to udev rules in boot image being different form the real thing.

Also default lvm.conf is used.

In journal it looks like LVs were activated before all PVs were scanned but that's likely just a timing issue with multiple processes output being gathered in different order.
Comment 3 Marian Csontos 2014-02-26 07:38:20 UTC 
Created attachment 867824 [details]
journal after the installation is over
Comment 4 Peter Rajnoha 2014-02-26 12:26:19 UTC 
Just FYI: the "token mismatch" error is also seen in recent bug #1069764 (F20). So the question is - how do we reach the situation in which "token mismatch" is returned? What are all the possibilities to get there?
Comment 5 Peter Rajnoha 2014-02-26 12:28:06 UTC 
What is the LVM layout used here exactly? (what are all the PV UUIDs used? So we can match them against the journal log...)
Comment 6 Marian Csontos 2014-02-27 08:51:31 UTC 
No longer reproducible with lvm2-2.02.105-7.el7.
Comment 7 Marian Csontos 2014-02-27 11:25:59 UTC 
Created attachment 868470 [details]
lvmdump

If anyone wants to dive deeper here's lvmdump.
Comment 8 Petr Rockai 2014-02-28 10:52:43 UTC 
Should have been fixed in 1769eddde7dcdd16716d646e14487cc1df6a3efc so it's good that it is no longer reproducible.
Note You need to log in before you can comment on or make changes to this bug.