I've seen this twice now in our environment where we have nodes that gets in a stuck state that we can neither manage or unmanage. They seem to do this after they have been put into a unmanaged schedule then somehow they are un/remanaged again by our users.
For example (below) a admin asked why they were paged when they unmanaged a node and did some reboots. I saw the node was showing as managed (green button not blue X) and it alerted when it went down due to the reboots. The Node only shows we can remanage it and clicking on remange does nothing.
I have been getting around this by bouncing services on the poller that is responsible for the node via Orion Service Manager. I dont like this workaround and was wondering if anyone has seen this or knows of a solution?
We are running: Orion Platform 2015.1.0, SAM 6.2.0, QoE 2.0, NCM 7.3.2, NPM 11.5, NTA 4.1.0, IVIM 2.0.0
Thanks