Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-13651

IP range and IP subnet scan fails on Assets Discovery 3.1.9

XMLWordPrintable

      Issue Summary

      Assets Discovery scan fails with "Object reference not set to an instance of an object" error.

      This is reproducible on Data Center: (yes)

      Steps to Reproduce

       
      Whenever a scan is executed with an IP range or an IP subnet, the scan fails in the host, the log shows:

      27/06/2023 16:29:03: [Normal] Object reference not set to an instance of an object.
   at Insight.Discovery.ProviderClasses.AssetProvider.GetHostInfoResultByKnownCredentials(List`1 knownCredentials, Int32 ttl, HostInfoDto additionalData, String ip) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE127-BUILD\ProviderClasses\AssetProvider.cs:line 221
   at Insight.Discovery.ProviderClasses.AssetProvider.GetHostInfo(String ip, Int32 port, Boolean usePowerShell, Int32 ttl, Boolean autoAddSudo, List`1 enabledPatternFiles, List`1 disabledPatternFiles, String scanSettingsEntryId, Boolean basicHostInfo) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE127-BUILD\ProviderClasses\AssetProvider.cs:line 136
      • The mentioned path, C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE127-BUILD\ProviderClasses\AssetProvider.cs doesn't exist in the machine running Discovery
      • The credentials test ok.
      • If the scan is done with a single IP, or placing the IPs separated by a semicolon the scan works properly.
      • Same scan settings on 3.1.8 work fine.

      Expected Results

      Scan to complete properly.

      Actual Results

      The below exception is thrown in the discovery log file:

      27/06/2023 16:29:03: [Error] Error scanning host
27/06/2023 16:29:03: [Normal] Exceptions:
27/06/2023 16:29:03: [Normal] Object reference not set to an instance of an object.
   at Insight.Discovery.ProviderClasses.AssetProvider.GetHostInfoResultByKnownCredentials(List`1 knownCredentials, Int32 ttl, HostInfoDto additionalData, String ip) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE127-BUILD\ProviderClasses\AssetProvider.cs:line 221
   at Insight.Discovery.ProviderClasses.AssetProvider.GetHostInfo(String ip, Int32 port, Boolean usePowerShell, Int32 ttl, Boolean autoAddSudo, List`1 enabledPatternFiles, List`1 disabledPatternFiles, String scanSettingsEntryId, Boolean basicHostInfo) in C:\build\DISCOVERY-DISCOVERYCLOUDRELEASE127-BUILD\ProviderClasses\AssetProvider.cs:line 136
27/06/2023 16:29:03: [Normal] Finish scan for 192.168.1.9

      Workaround

      Use Assets Discovery 3.1.8.

            [JSDSERVER-13651] IP range and IP subnet scan fails on Assets Discovery 3.1.9

            Sergio Soto Lopez made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 931008 ]
            Leonardo Souto made changes -
            Summary Original: IP range and IP subnet scan fails on Assets Dicovery 3.1.9 New: IP range and IP subnet scan fails on Assets Discovery 3.1.9
            Zakhar Listiev made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Zakhar Listiev made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            SET Analytics Bot made changes -
            Support reference count Original: 12 New: 13
            SET Analytics Bot made changes -
            Support reference count Original: 11 New: 12
            SET Analytics Bot made changes -
            UIS New: 1
            SET Analytics Bot made changes -
            Support reference count Original: 9 New: 11
            Satej Mirpagar made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 783995 ]
            Satej Mirpagar made changes -
            Assignee New: Zakhar Listiev [ 11507b174037 ]

              11507b174037 Zakhar Listiev
              09affdc70f32 Sergio Soto Lopez
              Affected customers:
              4 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: