CM Handle State: Retry CM-Handles that are LOCKED, Failed-to-Sync

Unreached CM-Handles status is updated as LOCKED with lock reason set to MISBEHAVING.

A new watchdog to be added to keep a check on LOCKED CM Handles and move them to ADVISED so the sync watchdog will progress them again!

see https://wiki.onap.org/display/DW/CPS-799+Spike%3A+Define+states+and+state+handling+for+CM+handle

The state for these misbehaving CM-Handles also need to be updated. A retry mechanism is required to updated the same. Conditions for cm -handles that should be retried:

1. CmHandleState = LOCKED
2. ChMhandleState.LocksReason = LOCKED_MISBEHAVING
3. DataStoreSyncState.Operational.state = UNSYNCHRONIZED

Question

• Frequency, 5 minutes?!
  • as long it is configurable
• Should we give up?
  • not for now, can be handled in future improvement

Acceptance Criteria :

1. Configurable wake-up time/ frequence
2. 'fake ' a misbehaving CMHandle -> watchdog processes should execute module sync for within ... minutes
3. All 'misbehaving' cm handles should best to 'ADVISED' in one go