locked
Opalis Warnings Result in SSP Errors RRS feed

  • Question

  • When we have the SSP launch an Opalis policy, it often occurs during or just before a reboot of the VM.  As a result, the first action of our Opalis policy has looping set on it so it can execute the action once the machine is back up.  Unfortunately, the SSP interprets Opalis' warnings as errors, and reports an error in the Job log in SSP.  Is there any way to tell the SSP that Opalis warnings are not errors, but in fact warnings?  We'd prefer that any reported warning doesn't get bubbled up to the SSP Job Log at all.  Errors, of course we want to know about as per usual.

    Thanks for any help!

    Tuesday, November 1, 2011 12:00 AM

All replies

  • Just bumping this up.  It's actually a serious issue for us since every time this occurs we have to assume the whole VM creation job has failed and tear it down and start over.  It eats up a lot of time (in relative terms) and causes a lot of questioning over whether we should be using this product.

    We are seeing this occur when Opalis reports a warning in a policy.  Often that warning will be because a looping object failed the first time but completed successfully the second time.  Opalis shows it as a warning, but the SSP reports it as an error.  I know we can click the "continue on errors" button in the SSP task, but that isn't helpful because there may actually be an error for which we do actually want to stop.

    Friday, December 16, 2011 1:52 AM