rgmanager does not start and triggers this error: "dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1"

Issue

Cluster node is able to join the cluster but as soon as rgmanager is started it gets hang an DLM producess following errors:

Jan 24 16:57:28 virt-242 corosync[2520]:   [QUORUM] Members[2]: 1 2
Jan 24 16:57:28 virt-242 rsyslogd-2177: imuxsock begins to drop messages from pid 2520 due to rate-limiting
Jan 24 16:57:31 virt-242 fenced[2581]: fenced 3.0.12.1 started
Jan 24 16:57:32 virt-242 dlm_controld[2605]: dlm_controld 3.0.12.1 started
Jan 24 16:57:33 virt-242 gfs_controld[2654]: gfs_controld 3.0.12.1 started
Jan 24 16:58:23 virt-242 rsyslogd-2177: imuxsock lost 783 messages from pid 2520 due to rate-limiting
Jan 24 16:58:23 virt-242 kernel: dlm: Using TCP for communications
Jan 24 16:58:23 virt-242 dlm_controld[2605]: open "/sys/kernel/dlm/rgmanager/id" error -1 30
Jan 24 16:58:23 virt-242 dlm_controld[2605]: open "/sys/kernel/dlm/rgmanager/control" error -1 30
Jan 24 16:58:23 virt-242 dlm_controld[2605]: open "/sys/kernel/dlm/rgmanager/event_done" error -1 30
Jan 24 16:58:23 virt-242 kernel: dlm: got connection from 2
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:23 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:24 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1
Jan 24 16:58:24 virt-242 kernel: dlm: invalid lockspace 5231f3eb from 2 cmd 2 type 1

Rgmanager fails to stop gracefully afterwards.