Notifications

131 views

Description

The "Test Account" functionality in Discovery Manager fails during creation of Cloud Resource Discovery schedule. It fails only when ECC Agent property "mid.sa.ssh.port" is set . The "Test Account" functionality is introduced from New York release.

Steps to Reproduce

  1. Set the mid server agent property "mid.sa.ssh.port" to "22" or any value.
  2. In Application navigator, type "Service Account"
  3. Open "Service Accounts" under Cloud Management
  4. Open the Cloud service account listed
  5. Click "Create Discovery Schedule" under "Related Links" and it will open "Discovery Manager"
  6. Once "Service Accounts" details populated, then click "Test Account"
  7. The "Test Account" fails.

The MID Server agent logs will show an error like this:

Worker-Interactive:HorizontalDiscoveryProbe-f525090b1ba1c8d40c9ab8c8dc4bcb08 Worker starting: HorizontalDiscoveryProbe source: Account Validation
Worker-Interactive:HorizontalDiscoveryProbe-f525090b1ba1c8d40c9ab8c8dc4bcb08 DEBUG: (104)ServiceWatchProbe - Task is running on MID server <MID Server Name>
Worker-Interactive:HorizontalDiscoveryProbe-f525090b1ba1c8d40c9ab8c8dc4bcb08 DEBUG: (104)PortScannerProvider - Starting port scan on host Account Validation. ports: 22
Worker-Interactive:HorizontalDiscoveryProbe-f525090b1ba1c8d40c9ab8c8dc4bcb08 DEBUG: (104)PortScannerProvider - Unknown host detected during port scan: Account Validation
Worker-Interactive:HorizontalDiscoveryProbe-f525090b1ba1c8d40c9ab8c8dc4bcb08 SEVERE *** ERROR *** (104)ServiceWatchProbe -
com.snc.sw.exception.HostDetectionFailedException: Failed to detect host Account Validation. Account Validation
at com.snc.sw.providers.PortScannerProvider.scanPorts(PortScannerProvider.java:61)
at com.snc.sw.providers.SSHProviderTerminal.findSshPort(SSHProviderTerminal.java:3047)
at com.snc.sw.providers.SSHProviderTerminal.setHost(SSHProviderTerminal.java:87)
at com.snc.sw.context.ExecutionContextFactory.create(ExecutionContextFactory.java:67)
at com.snc.sw.context.ExecutionContextFactory.create(ExecutionContextFactory.java:47)
at com.snc.sw.context.ExecutionContextFactory.createAppDiscovery(ExecutionContextFactory.java:145)
at com.snc.sw.context.ExecutionContextFactory.createAppDiscovery(ExecutionContextFactory.java:157)
at com.snc.sw.context.ExecutionContextFactory.createAppDiscovery(ExecutionContextFactory.java:163)
at com.service_now.mid.probe.HorizontalDiscoveryProbe.runProbe(HorizontalDiscoveryProbe.java:97)
at com.service_now.mid.probe.ServiceWatchProbe.probe(ServiceWatchProbe.java:35)
at com.service_now.mid.probe.AProbe.process(AProbe.java:103)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:122)
at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

The "Test Account" functionality to validate Cloud Service Account will fail in "Discovery Manager" UI with an on-screen message starting with:

Sensor error: ----------------------------- Stack: com.snc.sw.util.JSONUtil.fromJSONPlain(JSONUtil.java:96) com.snc.sw.discovery.HorizontalDiscoveryResult.fromJson(HorizontalDiscoveryResult.java:80) com.snc.sw.resulthandlers.HorizontalDiscoveryResultHandler.extractDiscoveryResult(HorizontalDiscoveryResultHandler.java:429) com.snc.sw.resulthandlers.HorizontalDiscoveryResultHandler.jsFunction_extractDiscoveryResults(HorizontalDiscoveryResultHandler.java:157) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:498) org.mozilla.javascript.MemberBox.invoke(MemberBox.java:138) org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:670) org.mozilla.javascript.FunctionObject.call(FunctionObject.java:614) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2582) org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) org.mozilla.javascript.gen.discovery_sensor_2f32f7899f230200fe2ab0aec32e706a_4485._c_anonymous_2(discovery_sensor.2f32f7899f230200fe2ab0aec32e706a:47) org.mozilla.javascript.gen.discovery_sensor_2f32f7899f230200fe2ab0aec32e706a_4485.call(discovery_sensor.2f32f7899f230200fe2ab0aec32e706a) org.mozilla.javascript.ScriptRuntime.doCall2(ScriptRuntime.java:2651) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2590) org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32) org.mozilla.javascript.gen.sys_script_include_778011130a0a0b2500c4595ad1d1d768_script_4488._c_anonymous_5(sys_script_include.778011130a0a0b2500c4595ad1d1d768.script:194) org.mozilla.javascript.gen.sys_script_include_778011130a0a0b2500c4595ad1d1d768_script_4488.call(sys_script_include.778011130a0a0b2500c4595ad1d1d768.script) org.mozilla.javascript.ScriptRuntime.doCall2(ScriptRuntime.java:2651) org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2590)

 

Workaround

  1. Go on ecc_agent_property.LIST
  2. Create a new property:
    1. mid.sa.ssh.port
    2. Keep the value as empty.
    3. MID Server = "The mid server you are using for the Test account service

Related Problem: PRB1373912

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - ITOM - Cloud Management Google Cloud Connector - v1.0
SR - ITOM - Cloud Management Terraform Connector - v1.1
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - VR - Qualys - New York 2019 Q3
SR - VR - Vulnerability Response - New York 2019 Q3

Intended Fix Version

Paris

Fixed In

New York Patch 7
Orlando Patch 1

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-03-17 14:13:35
Published:2019-12-17