Comment 3 for bug 1362659

Aleksey Kasatkin (alekseyk-ru) wrote :

The problem arrives on update cluster created with 5.0 master node to 5.0.2 using new (5.1) master node.