tree 76a8e093afee41e5623aac7a490d3ebe05664176
parent a9b2b1d16797fefa4c7be8ba0bf01f0fdab22b7b
author Jim Hahn <jrh3@att.com> 1534445835 -0400
committer Jim Hahn <jrh3@att.com> 1534515808 -0400

fix new sonar issues with prov-status check

Changes made while adding the prov-status check triggered some sonar
thresholds in ControlLoopEventManager.  Updated the code to resolve
them.  One of the changes that had been introduced was to check for
the existence of both the is-closed-loop-disabled AND the prov-status
fields.  However, if one is there then the other should be there, thus
the second check is redundant and was removed, which should reduce the
cyclomatic complexity back under the threshold.
Re-ordered the code a little, to make it less ambiguous.
Removed trailing white space.

Change-Id: If0ce74cedbf947c32cae3df3374cda6ba1305cd2
Issue-ID: POLICY-964
Signed-off-by: Jim Hahn <jrh3@att.com>