Deleting the compute service via the api should fix this as long as you have the fix from bug 1756179. Of course the question now is when/what is the right time/place to do that delete (safely).
Deleting the compute service via the api should fix this as long as you have the fix from bug 1756179. Of course the question now is when/what is the right time/place to do that delete (safely).