Processes group profile changes are not reflecting in the devices in CU6

Products

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

Issue/Introduction

We discovered that unwanted QoS was enabled in the setup processes profile. Although we removed the QoS and redeployed the group profile, the changes are not reflecting on the devices. While the device-level process setup profile shows that it has been updated, the changes are not taking effect. 

Environment

• DX UIM 23.4 CU6
• processes probe

Resolution

Engineering created a patch for mon_config_service in CU6 to reconcile the device-level with the group-level settings. The build is MCS hotfix v23.4.6.3 and it is attached to this article.

This patch has the fix the following cases:

• Template migration to 5.01 version

• Group profile changes are not reflecting at the device level. For this, some cleanup required using the new diagnostic/cleanup callback: find_overridden_device_profiles_group
  
  What it does: Lets an administrator find device-level monitoring profiles whose configuration values differ ("are overridden") from the group-level template they inherit from — and optionally clean those overrides up in the same call. Useful for auditing configuration drift after a template change, or for resetting devices back to group-standard configuration in bulk.

• Input parameters (all optional, but at least one of the first three is required):
  
  
  • groupProfile_id    A specific profile ID (device- or group-level) to check
  • Template_Name    Name of a production probe template — scopes the search to profiles using that template
  • group_name    A device group, by name or by numeric group ID — scopes the search to that group
  • perform_cleanup    yes/true to delete the overridden values and mark the profile modified; omitted (or anything else) runs as a report-only, no-changes dry run

    Set perform_cleanup to false or empty for dry run and to list what are the device profiles having this issue.

  • Pass true to clean a profile.

As a first step, run the callback for a group profile Id with perform_cleanup = false to list device profiles. Review the list of profiles and if they match the devices with issues, set perform_cleanup = true and rerun the callback for cleanup.

To cleanup all profiles of a Template on all groups, simply pass the template name. Don't pass the group name or profile ID.