Alarm policies are not being updated due to errors

Products

• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management for z Systems
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• DX Infrastructure Management

Issue/Introduction

- The issue is when there are multiple policy management nodes being processed, only one node can process the alarm policies. However, this will cause other nodes to error causing exceptions in the log files.

 

- Errors in policy_management.log below

2021-03-26 16:11:37,730 DEBUG com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:243 [Timer-0]   - Registering the policy node to [email protected]://#.#.#.#:443/adminconsoleapp
2021-03-26 16:11:37,743 ERROR com.ca.uim.policy.management.events.service.HeartBeatService:registerThisNode:307 [Timer-0]   - Registration of this policy node to master failed, javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Cause

- Policy processing is failing due to multiple nodes

Environment

Release : 20.3

Component : UIM - ALARM POLICY

Resolution

-This patch (policy_management_ws_0.27T1.zip) fixed the issue allowing multiple-nodes to process the policies.

Additional Information

Fix: policy_management_ws_0.27T1.zip
Release Date: 25-Jun-2021
Applicable for: UIM 20.3.0+

This patch addresses the following:
- Policy processing is failing in https environment.

Dependencies/Prerequisites:
None

Steps to apply the patch:
1. Import the zip into the local archive.
2. Deploy the imported package to the robot's running policy_management_ws

Additional steps:
a. If the policy_processing flag is set in wasp.cfg > webapps/policy_management_ws/custom/uncrypted/policy_processing to true, policy processing will happen, if set to false, processing will not happen. This is the manual way of configuration.

b. In a load balanced environment with multiple policy_management_ws nodes, the policy_processing should happen in an HA mode. For that, webapps/adminconsoleapp/custom/uncrypted/ha_mode should be set to true and all the policy_management_ws nodes should not have the policy processing flag. Then, nodes will be selected dynamically and work in HA mode.

c. In a https environment, please add the configuration parameter-> "controller_url = https://FQDN/Certname:9443/adminconsoleapp" under wasp.cfg > webapps/policy_management_ws/custom/unencrypted, to avoid certificate issues.