Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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.
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?
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: