Search Engine: Elastic

Article ID: 132154, created on Jan 29, 2018, last review on Feb 9, 2019

  • Applies to:
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3
  • Operations Automation 7.4

Symptoms

Provider removed a service node from OA. Task Cleanup packages on host fails with error:

Internal error: Unexpected query result: 0.

Depending on OA version, the task output can also be:

Internal error: HTTP POST to 'https://192.168.0.10:8352/process' failed: javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request org.apache.http.NoHttpResponseException: 192.168.0.10:8352 failed to respond

The error is registered in /var/log/pa/core.log right after function getSC in scope of os_config removal:

Jun 20 08:50:58.271 : DBG [task:3996824:1356 Thread-40-(ActiveMQ-client-global-threads-352684240):915 pau]: c.p.p.s.y.e.OperationProcessorBean prepare deinstall for component 931 (os_config-other)
...
Jun 20 08:50:58.356 : DBG [task:3996824:1356 p:-default-threadpool;-w:-Idle:731 pau]: c.p.p.tracer entry: com.parallels.pa.service.naming.ejb.ResolverBean.getSC(136)
Jun 20 08:50:58.366 : DBG [task:3996824:1356 p:-default-threadpool;-w:-Idle:731 pau]: c.p.p.tracer exit by exception: com.parallels.pa.service.naming.ejb.ResolverBean.getSC java.lang.RuntimeException: Unexpected query result: 0

Cause

This is a result of software-related issue #FND-3562

Resolution

Contact your Technical Account Manager or Pooled Technical Associates team (pta@cloudblue.com) to trace the status of request #FND-3562 and apply an internal workaround.

31987597efff5a3a9ce779cc203bbe5e 8fc71f07abe5b233fea1ae0377cd5e3d 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 8c199f0ee4305da1a577740620df4a51 dd79f16c76b9dca75205ab5e9f5465ea 55fe109b4b4fe3fbb893f22dbb85a41a

Email subscription for changes to this article
Save as PDF