Notifications

1716 views

Description

When running Cloud Discovery for AWS, the following error appears in the Discovery log for the pattern Amazon AWS Route53 HD: 

Failed Exploring CI Pattern, Pattern name: Amazon AWS Route53 HD, To Check Pattern Log Press Here.

The following error appears in the Pattern log:

2018-07-02 00:16:16: Identification Engine: Discovery status is FAILURE, CI Type cmdb_ci_dns_name cannot be created since there are no attributes defined. Debug pattern to understand why no attributes have been assigned.

Steps to Reproduce

  1. Configure Cloud Discovery for AWS.

    For more information, see the product documentation topic Cloud discovery.

  2. Run Discovery.

    Note the errors in the Discovery log and Pattern log.

 

Workaround

You can ignore the error in the Discovery log, or you can resolve it by using the following workaround.

Note: Once the pattern is changed, it will not be automatically updated during platform upgrade. 
Therefore, if you upgrade to a version that contains a fix to this issue, revert the pattern to the default out of box version for the fix version.

  1. Navigate to Discovery Patterns and open Amazon AWS Route53 HD.

  2. Click on the link "ID route53" in the Identification section.

  3. Add a step below "4. Get specific per hostedZone" with the following information:

    Operation: Match 
    $info_table Is Not Empty
    Termination Type is Expected
    Information Message is: No Zone Information discovered.
    Pattern stopped. 

  4. Save the pattern and then Publish.

 

 


Related Problem: PRB1293297

Seen In

London
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - Discovery and Service Mapping - 201908
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - SIR - VirusTotal Integration - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Fixed In

Kingston Patch 8
London Patch 1
Madrid

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-08-19 06:58:58
Published:2018-07-17