ERP and STP interaction after OS9702E reload

[alexC]

We have several OS9702E with AOS 6.4.6.340 in a ring topology and use ERPv2 to prevent loops. When one of these OS9702E is reloaded in the case of maintenance works we see huge amount of STP error messages in swlogs during approximately 10 minutes after the reload. For example:

TUE AUG 16 16:30:34 2016 STP error stpCMM_linkAggVpaUpdate API 5 vlan 40000101 ifindex is a ERP port
TUE AUG 16 16:30:35 2016 STP error stpCMM_linkAggVpaUpdate API 6 vlan 40000101 ifindex is a ERP port
TUE AUG 16 16:30:36 2016 STP error stpCMM_linkAggVpaUpdate API 7 vlan 40000101 ifindex is a ERP port
TUE AUG 16 16:30:37 2016 STP error stpCMM_linkAggVpaUpdate API 8 vlan 40000101 ifindex is a ERP port
TUE AUG 16 16:31:04 2016 STP error stpCMM_linkAggVpaUpdate API 5 vlan 40000102 ifindex is a ERP port
TUE AUG 16 16:31:05 2016 STP error stpCMM_linkAggVpaUpdate API 6 vlan 40000102 ifindex is a ERP port
TUE AUG 16 16:31:06 2016 STP error stpCMM_linkAggVpaUpdate API 7 vlan 40000102 ifindex is a ERP port
TUE AUG 16 16:31:07 2016 STP error stpCMM_linkAggVpaUpdate API 8 vlan 40000102 ifindex is a ERP port

40000101 and 40000102 are lacp LAGs 101 and 102, through which ERPv2 ring is working, and 5,6,7,8 are vlans in these LAGs. I think these messages come because STP can't work on the same ports on which ERP is working and some inconsistency can be between these protocols in a short time after the reload. Maybe somebody already faced with that issue and knows how to avoid these messages? I made a lab and tried to disable STP on the LAGs manually using command "bridge 1x1 vid logical_port disable" but it was not help.