BugZero | ServiceNow BugID PRB1786820 - [External] Discovery Schedules can become hung in ...

ServiceNow - Defect ID: PRB1786820

[External] Discovery Schedules can become hung in duplicate IP processing due to duplicate device histories for same IP

ServiceNow - Defect ID: PRB1786820

[External] Discovery Schedules can become hung in duplicate IP processing due to duplicate device histories for same IP

Last updated on November 21st, 2024

BugZero Risk Score
6.7 Medium

Overall: 6.7

Severity: 7.3

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: Sev2
Article Views: 724
Affected Component: Discovery

Description

You note that when discovering servers with multiple NICs, sometimes Discovery will become hung if you are discovering independent applications (ex: Kafka) or hardware (ex: UNIX Cluster) Steps to Reproduce - Enable IP dedupe processing - Scan Server with multiple NICs - Have a pattern triggered from ADM where the CI class is independent (ex: Kafka) - Test until Kafka DH is selected for IP dedupe and note that "Skip IP" classify input is hung

Workaround

Apply attached script include workaround. Validated only for Visibility Content 6.19 and 6.19.1

Related Problem

PRB1786820

Change history

2024-11-21 Added: Utah Patch 10b Hot Fix 1, Utah Patch 10b Hot Fix 2, Vancouver Patch 10, Vancouver Patch 10 Hot Fix 1, Vancouver Patch 10 Hot Fix 2, Vancouver Patch 2 Hot Fix 1, Vancouver Patch 4, Vancouver Patch 4 Hot Fix 1b, Vancouver Patch 6 Hot Fix 2, Vancouver Patch 7 Hot Fix 1, Vancouver Patch 7 Hot Fix 3b, Vancouver Patch 8 Hot Fix 2, Vancouver Patch 8 Hot Fix 4, Vancouver Patch 9 Hot Fix 2, Vancouver Patch 9 Hot Fix 2a, Washington DC Patch 3 Hot Fix 1, Washington DC Patch 3 Hot Fix 2, Washington DC Patch 4, Washington DC Patch 4 Hot Fix 1, Washington DC Patch 4 Hot Fix 1a, Washington DC Patch 4 Hot Fix 2, Washington DC Patch 5, Washington DC Patch 5 Hot Fix 1, Washington DC Patch 5 Hot Fix 2

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Relevant Products

Click on a version to see all relevant bugs

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 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

ServiceNow - Defect ID: PRB1786820

[External] Discovery Schedules can become hung in duplicate IP processing due to duplicate device histories for same IP

ServiceNow - Defect ID: PRB1786820

[External] Discovery Schedules can become hung in duplicate IP processing due to duplicate device histories for same IP

Last updated on November 21st, 2024

BugZero Risk Score6.7 Medium

Bug Details

Description

Workaround

Related Problem

Links

Top ServiceNow Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
6.7 Medium