Loading...
Loading...
The discovery model's "Discovered Product" doesn't match its software installation's "Display Name" when the override edition or version (or any other primary key field) is updated after the software install has already been normalized or partially normalized. Steps to Reproduce 1. Create a software installation. 2. Normalise the discovery model for the install. 3. Update the edition override field in the install. 4. This causes the primary key to update and trigger the BR "Create a Software Normalization" on the software installation table. or 1. When the version is updated on the application CI. On the associated software installation, the version is updated. 2. Note: The discovery model for the install is normalized before the version updated. 3. This causes the primary key to update and trigger the BR "Create a Software Normalization" on the software installation table.
As a workaround, please run the fix script [via Scripts - Background] to fix the existing issue discovery models and apply the attached update set [sys_remote_update_set_c156aa729ff3e610e36f08166924abb4.xml]. Once the fix script is completed, please make sure to run the scheduled job "SAM - Normalize discovery models using content library rules" to normalize the discovery models updated. This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.
PRB1857676
Click on a version to see all relevant bugs
ServiceNow Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.