Current behavior

Created CmHandle stuck in ADVISED state if it was created, deleted and created again.

If we register a cmHandle, than delete it, than register it again, it will stuck in ADVISED state and will never go to READY

It is a blocker for us because we perform cmhandle create-delete-create several times

Expected behavior

Cmhandle registration should work and it should be able to go to READY state even if it was created and deleted before.

Reproduction

• Register a cmHandle
• Wait until it goes to READY state from ADVISED
• Delete the cmHandle
• Wait until it is removed
• Register the cmHandle again

Logs:

No error during first creation.

No error during removal.

Logs at second creation:

    Schema set D09D6160CF25A5DCF97180B36FDE8F62 does not exist or already deleted
    Total number of fetched advised cm handle(s) is (are) 1               

Workaround

After NCMP pod restart it was able to handle the cmHandle in ADVISED state and move it to READY

CPS version

I tested with the master where the last commit was  https://gerrit.onap.org/r/gitweb?p=cps.git;a=commit;h=8d7cfc4545c3bd2efbad1eb1e5ea0cb0fcf8568c
This was the last commit before huge CPS1126 changes