Another case of "SREP: FSM: no such a transition COMMITTING -> ROLLED_BACK"

We are seeing another case where Galera aborts with

SREP: FSM: no such a transition COMMITTING -> ROLLED_BACK

None of the causes known from other bug reports (MDEV-10259, MDEV-10391, launchpad bug #1404168) seems to apply here (no encryption, no replication, no innodb_fake_canges)

What may be related to the issue in this case may be a high number of Rx package drops on the underlying network though, no further incidents seem to have occurred so far since this network issue has been fixed.

As this assertion error can be hit via so many different ways it seems that either the direct transition from COMMITTING to ROLLED_BACK state is actually a valid one, or that we have a substantial general problem with transaction state tracking that can lead to mysqld crashes in many different ways ?