Bug 1740944
| Summary: | WARNING: Not using lvmetad because cache update failed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Corey Marthaler <cmarthal> | ||||
| Component: | lvm2 | Assignee: | David Teigland <teigland> | ||||
| lvm2 sub component: | Default / Unclassified | QA Contact: | cluster-qe <cluster-qe> | ||||
| Status: | CLOSED ERRATA | Docs Contact: | |||||
| Severity: | medium | ||||||
| Priority: | urgent | CC: | agk, bubrown, bwelterl, heinzm, jbrassow, mcsontos, mknutson, msnitzer, patrick.vo, pdwyer, prajnoha, rhandlin, teigland, trinh.dao, yzheng, zkabelac | ||||
| Version: | 7.7 | Keywords: | Triaged | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | lvm2-2.02.187-1.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-09-29 19:55:48 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1689420, 1704833, 1715931, 1821862 | ||||||
| Attachments: |
|
||||||
|
Description
Corey Marthaler
2019-08-13 23:20:58 UTC
related to bug 1672336 *** Bug 1712125 has been marked as a duplicate of this bug. *** Here is a new commit that may resolve some more of the lvmetad problems: https://sourceware.org/git/?p=lvm2.git;a=commit;h=5d6bf1efb225b964bfff398277e68345acdac1d0 David, will this commit going to included in next RHEL7.8 snapshot 1 build? thanks, trinh I doubt that the commit in comment 7 it is included in 7.8 since that commit is quite recent. Thank you David for the update! Monte, since there is commit, can RH change the status to POST or MODIFIED? can you check if commit makes it in the next RHEL7.8 snapshot 1 release? David, will the fix be included in RHEL7.8 snapshot-5 release on 2/18? thanks, trinh I checked dist-git and it is not included AFAICT. I'm not sure how these kinds of things get flagged to get the attention of people who can approve them. We have missed this one for rhel7.8. The warning should not affect operation. This will be fixed for 7.9. We also have the option of fixing in a 7.8 zstream update, which would allow the fix to be had before a 7.9 release. Please advise if this is desired. RH, is this bug fixed in RHEL7.8 GA? thanks, trinh I'm not sure, but I suspect it might since it was added to the errata in a previous comment. Hi David, HPE engineer PatrickV retested with RHEL7.8GA and still see the same error message. thanks, trinh I'm not seeing the commit from comment 7 in rhel7, but we don't really have anything specific linking that commit to the errors seen here, so it may be worthwhile to collect the messages from the failing boot again, including systemctl status -f -n 1000 lvm2-* (which should include some extra info in the new version.) Patrick, can you please collect info in comment 21 need to debug this issue? thanks, trinh Created attachment 1679159 [details]
lvmetad
Thanks, that output was helpful, were all the VGs properly autoactivated in spite of the two lvm2-pvscan services that report failures? Could you try a test package if I built one that includes the missing patch? I'm not sure I can test it since the issue I'm seeing is on boot to install, BZ 1712125. Can someone check if all the VGs were activated? It appears so, in which case this is just an issue of changing the exit code to avoid reporting an error in the service when there was none. Marking this verified in the latest rhel7.9 rpms. We didn't see this error on the machines doing rhel7.9 regression testing that we did in rhel7.8. [root@mckinley-01 ~]# grep "cache update failed" /var/log/message* [root@mckinley-01 ~]# lvm2-2.02.187-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 lvm2-libs-2.02.187-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 lvm2-cluster-2.02.187-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 lvm2-lockd-2.02.187-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 device-mapper-1.02.170-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 device-mapper-libs-1.02.170-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 device-mapper-event-1.02.170-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 device-mapper-event-libs-1.02.170-5.el7 BUILT: Sun Jun 7 08:13:11 CDT 2020 device-mapper-persistent-data-0.8.5-3.el7 BUILT: Mon Apr 20 09:49:16 CDT 2020 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 (lvm2 bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3927 |