-
Bug
-
Resolution: Done-Errata
-
Blocker
-
None
-
rhel-8.4.0.z
-
None
-
None
-
Critical
-
rhel-sst-cs-databases
-
None
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
-
x86_64
-
None
Problem Statement | InnoDB: WSREP: referenced FK check fail: Lock wait index Export |
Description | What are you experiencing? What are you expecting to happen? After upgrading the mariadb version from 10.3.32 to 10.5.9 which is available in the 8.4 EUS, we are seeing the below errors in the mariadb.log files periodically. 2023-10-05 9:55:31 48240 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 10:13:37 56562 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 10:31:31 64840 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 10:32:57 65330 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`ml2_port_bindings` 2023-10-05 10:46:49 71714 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 10:49:08 73131 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`ml2_port_binding_levels` 2023-10-05 10:49:25 73312 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 10:51:00 73964 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`ml2_port_binding_levels` 2023-10-05 11:07:29 81692 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks` 2023-10-05 11:43:37 98366 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks Define the value or impact to you or the business This DB upgrade step is required for us to upgrade our RHOSP platform from 16.2 to 17.1. This may become a blocker for the RHOSP 17.1 upgrade if not addressed. Where are you experiencing this behavior? What environment? Stage environment. |