It would seem that the problem causing this bug was fixed together with the foreign key issue, as detailed in comments in http://www.mysqlperformanceblog.com/2013/01/30/announcing-percona-xtradb-cluster-5-5-29-23-7-1/#comment-1242845.
Also, as of the upcoming Percona XtraDB Cluster 5.5.33, the bug seems no longer reproducible un updates to 5.5.33.
Marking as Fix Comitted for now, if you find any issues or you are able to reproduce it under some circumstances please let us know.
It would seem that the problem causing this bug was fixed together with the foreign key issue, as detailed in comments in http:// www.mysqlperfor manceblog. com/2013/ 01/30/announcin g-percona- xtradb- cluster- 5-5-29- 23-7-1/ #comment- 1242845.
Also, as of the upcoming Percona XtraDB Cluster 5.5.33, the bug seems no longer reproducible un updates to 5.5.33.
Marking as Fix Comitted for now, if you find any issues or you are able to reproduce it under some circumstances please let us know.