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 1899052 - InnoDB: WSREP: referenced FK check fail: Lock wait index Export
Summary: InnoDB: WSREP: referenced FK check fail: Lock wait index Export
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: mariadb
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Michal Schorm
QA Contact: RHEL CS Apps Subsystem QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-18 13:41 UTC by Michael Bayer
Modified: 2021-01-04 11:16 UTC (History)
2 users (show)

Fixed In Version: mariadb-server-10.3.27-3.module+el8.3.0+8972+5e3224e9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-04 11:15:53 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Bayer 2020-11-18 13:41:31 UTC 
Description of problem:

in openstack we are seeing the impacts of https://jira.mariadb.org/browse/MDEV-18562 , a concerning message in the logs related to WSREP.  it has been fixed in mariadb 10.2.28/10.3.19

Version-Release number of selected component (if applicable):

10.3.17

How reproducible:

varies

Steps to Reproduce:
1. see bz#1898707 for environment information
2.
3.

Actual results:

errors in the log that don't seem to impact the application server:

2020-11-17  6:39:24 171356 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `ix_workers_service_id` table `cinder`.`workers`
2020-11-17  6:39:32 171283 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `ix_workers_service_id` table `cinder`.`workers`
2020-11-17  7:42:46 184320 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `fk_stack_id` table `heat`.`sync_point`
2020-11-17  7:43:00 184585 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `fk_stack_id` table `heat`.`sync_point`
2020-11-17  7:43:24 184648 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `fk_stack_id` table `heat`.`sync_point`
2020-11-17  8:33:44 184050 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `ix_workers_service_id` table `cinder`.`workers`

etc

Expected results:

no error messages in the log

Additional info:
Comment 1 Honza Horak 2021-01-04 11:15:53 UTC 
Advisory RHSA-2020:5500 shipped 10.3.27, so I believe it is now fixed in RHEL-8.3.0.
https://access.redhat.com/errata/RHSA-2020:5500

Please, feel free to re-open if the problem persists.
Note You need to log in before you can comment on or make changes to this bug.