16 views

Description

Issue 1:
step 9 is filtering application gateway, however application gateway service is not filtered
as a result when pattern runs it has error lb service doesn't have relation to application gateway.


Issue 2:
As in issue 1>, after both gateway and service are filtered, the public IP and private IP are not.
The merge at step: 17,18,20,21 are keep, not remove. As a result some invalid IPs are kept and used as service eventually, causing same error: service doesn't have relation to application gateway.

Steps to Reproduce

Set up and run discovery schedule for Azure service account that can trigger Azure Application gateway pattern


Workaround

There is no known workaround for this issue. If you are able to upgrade, review the "Intended Fix Version" section below below to determine the versions that have a permanent fix.

If you have any question, please create a support case.


Related Problem: PRB1435311

Seen In

There is no data to report.

Intended Fix Version

SR - ITOM - Discovery and Service Mapping - 202012

Safe Harbor Statement

This "Intended Fix Version" information is meant to outline ServiceNow's general product direction and should not be relied upon in making a purchasing decision. The information provided here is for information purposes only and may not be incorporated into any contract. It is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at ServiceNow's sole discretion.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-10-21 15:24:47
Published:2020-10-21