Overview
During an internal code review we have found a bug in the check ServiceProcessor . The present version will exit with OK even if errors werde found (false negative).
Mitigation
Customers using the check ServiceProcessor to monitor the status of the internal service processors (all other checks are not affected) should not rely on the exit code of that check but carefully study the checks message (stdout).
Example
NETAPP\_PRO SERVICEPROCESSOR OK - 1 service-processor checked
sim92-01: unknown (version n/a, ip is NOT configured, autoupdate is NOT enabled)
```The message clearly states that several aspects are not ok - but the check still exits with OK.
Solution
--------
We are working on an update. Customers relying on the ServiceProcessor check should update when this fix has been released. We will post the availability of that update here on the blog. ([Subscribing](https://blog.netapp-monitoring.info/register/) to the blog is recommended anyway.)
Comments