I looked at the logs again, it actually didn't have the 2nd issue that a uncontrolled swact started before the other controller was enabled. it was a service failure-recovery on a single controller (as SM did not receive the controller-1 being enabled msg, SM on controller-0 had controller-1 state as unlocked-failed). with a 5 minutes debounce wait time.
I looked at the logs again, it actually didn't have the 2nd issue that a uncontrolled swact started before the other controller was enabled. it was a service failure-recovery on a single controller (as SM did not receive the controller-1 being enabled msg, SM on controller-0 had controller-1 state as unlocked-failed). with a 5 minutes debounce wait time.
| 2019-08- 14T16:09: 16.662 | 1252 | service-group-scn | vim-services | disabled | go-active | 14T16:09: 24.369 | 1384 | service-group-scn | vim-services | go-active | active | 14T16:14: 33.679 | 1485 | service-group-scn | vim-services | disabled | go-active | 14T16:14: 41.673 | 1617 | service-group-scn | vim-services | go-active | active | 14T16:19: 46.528 | 1718 | service-group-scn | vim-services | disabled | go-active | 14T16:19: 54.490 | 1850 | service-group-scn | vim-services | go-active | active | 14T16:25: 03.220 | 1951 | service-group-scn | vim-services | disabled | go-active |
| 2019-08-
| 2019-08-
| 2019-08-
| 2019-08-
| 2019-08-
| 2019-08-
A vim patch should fix the issue reported.