Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1991341

Summary:	mysqld got signal 6, "WSREP: invalid state ROLLED_BACK (FATAL)"
Product:	Red Hat Software Collections	Reporter:	Flos Qi Guo <qguo>
Component:	mariadb	Assignee:	Zuzana Miklankova <zmiklank>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jakub Heger <jheger>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rh-mariadb103	CC:	databases-maint, hhorak, jheger, ljavorsk, mmuzila
Target Milestone:	alpha	Keywords:	Triaged, ZStream
Target Release:	3.7	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	2050518 2050520 (view as bug list)		Environment:
Last Closed:	2022-04-14 13:07:29 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:	2050518, 2050520

Description Flos Qi Guo 2021-08-09 04:54:23 UTC

> Description of problem:
mysqld aborted with message "[ERROR] WSREP: invalid state ROLLED_BACK (FATAL)"

> Version-Release number of selected component (if applicable):
rh-mariadb103-mariadb-server-10.3.28-2.el7.x86_64

> How reproducible:
MariaDB 10.3.28 with Galera (Software Collections) is periodically crashing due to a SIGABRT signal. Issue began after updating from 10.3.27.

> Steps to Reproduce:
1. Update MariaDB from 10.3.27 to 10.3.28 with Galera
2. Restart MariaDB
3.

> Actual results:
MariaDB aborted with errors.

> Expected results:
MariaDB should not abort.

> Additional info:
Seems like ustream's issue:
 - https://jira.mariadb.org/browse/MDEV-25114