BugZero | ServiceNow BugID PRB1629996 - Per Core Calculator

BugZero | ServiceNow BugID PRB1629996 - Per Core Calculator - if a cluster only has SQL Se...

ServiceNow - Defect ID: PRB1629996

Per Core Calculator - if a cluster only has SQL Server components but no SQL Server parent installs, the VMs in the cluster are processed at host level and not at a cluster level [Already fixed in Tokyo]

ServiceNow - Defect ID: PRB1629996

Per Core Calculator - if a cluster only has SQL Server components but no SQL Server parent installs, the VMs in the cluster are processed at host level and not at a cluster level [Already fixed in Tokyo]

Last updated on December 19th, 2022

BugZero Risk Score
5.8 Medium

Overall: 5.8

Severity: 6.4

Community: 3.7

Lifecycle: 8.2

What is the BugZero Risk Score?

ServiceNow Integration

Learn more about where this data comes from

ServiceNow Integration

Learn more

Bug Scrub Advisor

Streamline upgrades with automated vendor bug scrubs

Bug Scrub Advisor

Learn more

BugZero Enterprise

Wish you caught this bug sooner? Get proactive today.

BugZero Enterprise

Learn more

Bug Details

Priority: Sev3
Article Views: 13
Affected Component: Asset Management

Description

Per Core Calculator - if a cluster only has SQL Server components but no SQL Server parent installs, the VMs in the cluster are processed at host level and not at a cluster level. Apart from other license compliance issues it can lead to, it also leads to the cluster column being empty on the License Required By records. Steps to Reproduce - a cluster only has SQL Server components but no SQL Server parent installs - check the SQL Server -> License Required

Workaround

This issue is under investigation of Dev team. A workaround has been provided in attached file.

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:San Diego Patch 1 Hot Fix 1, San Diego Patch 10, San Diego Patch 10 Hot Fix 1, San Diego Patch 10 Hot Fix 1a, San Diego Patch 10 Hot Fix 1b, San Diego Patch 10 Hot Fix 2b, San Diego Patch 3, San Diego Patch 7a, San Diego Patch 7b, San Diego Patch 9, San Diego Patch 9a, San Diego Patch 9b, Utah, Vancouver

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top ServiceNow Defects

9.4Defect ID: PRB1954123
Instance access issues due to Mutual TLS (mTLS) enablement on Zurich instances
8.5Defect ID: PRB1611377
CMDB Baseline creation job causing app node out of memory when a CI has a huge number of records referencing it
8.5Defect ID: PRB1788540
AWS Events Driven discovery is overloading Default Semaphores.
8.5Defect ID: PRB1871576
Data visualization can be accessed by anyone with URL to visualization designer
8.5Defect ID: PRB1928008
Upgrade to Yokohama releases can hang for Haraka enabled instance because of contention on kagami query registrar

Ready to prevent the next vendor outage?

Get a demo

ServiceNow - Defect ID: PRB1629996

Per Core Calculator - if a cluster only has SQL Server components but no SQL Server parent installs, the VMs in the cluster are processed at host level and not at a cluster level [Already fixed in Tokyo]

ServiceNow - Defect ID: PRB1629996

Per Core Calculator - if a cluster only has SQL Server components but no SQL Server parent installs, the VMs in the cluster are processed at host level and not at a cluster level [Already fixed in Tokyo]

Last updated on December 19th, 2022

BugZero Risk Score5.8 Medium

Bug Details

Description

Workaround

Related Problem

Links

Top ServiceNow Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
5.8 Medium