An SLO object kicks off twice in a client even though it is only defined once. OR the SLO object continues to kick off even though it has been deleted.
The following was done to move clients into client 100 from a different Automic system:
One time when this was done, the same SLO was kicking off notifications twice. At another point, that SLO object had been deleted from the system but continued to be fulfilled and activate notifications – these notifications also restarted some objects even though they should not have been (because the SLO should not have activated anything when it was deleted)
Release : 12.3.7
Root cause was not found for this. It looks like at some point the JWP had a cached value of the original SLO object. The JWP is the process that keeps track of and processes SLO objects. When the SLO seemed to be getting fulfilled twice and kicking off double notifications, this would be when the original SLO was cached and the actual SLO was also kicking off notifications. When we deleted the actual SLO object, the cached SLO was still kicking off notifications. Since the JWP holds the SLO processes, restarting the server seems to uncache the original SLO object.
If this happens again, the following should be done: