-
Bug
-
Resolution: Unresolved
-
Medium
-
Guilin Release, Honolulu Release
-
None
-
ONAP/Guilin, SO 1.7.10
It looks like SO-OpenStack-Adapter is constantly trying to retrieve the ExternalTask status, even of no system for external task handling is integrated. This results in observing the following exception in the so-openstack-adapter debug.log:
2020-12-28T12:07:34.853Z|2a62620a-c9d3-4d7f-8fc5-6c323d5a2a0a|org.onap.so.adapters.vnf.VnfAdapterUtils - Got CloudSite: Optional[CloudSite_.._jvst398_0[regionId=k8sRegion,identityServiceId=DEFAULT_KEYSTONE,cloudVersion=2.5,clli=WL_3G,cloudifyId=<null>,platform=<null>,orchestrator=multicloud,cloud-owner=<null>]]
2020-12-28T12:07:34.853Z|2a62620a-c9d3-4d7f-8fc5-6c323d5a2a0a|org.onap.so.adapters.vnf.VnfAdapterUtils - GetVnfAdapterImpl: mode=MULTICLOUD
2020-12-28T12:07:34.928Z||org.camunda.bpm.client - TASK/CLIENT-03001 Exception while fetch and lock task.
org.camunda.bpm.client.impl.EngineClientException: TASK/CLIENT-02002 Exception while establishing connection for request 'POST http://so-bpmn-infra.onap:8081/sobpmnengine/external-task/fetchAndLock HTTP/1.1'
at org.camunda.bpm.client.impl.EngineClientLogger.exceptionWhileEstablishingConnection(EngineClientLogger.java:35)
at org.camunda.bpm.client.impl.RequestExecutor.executeRequest(RequestExecutor.java:98)
at org.camunda.bpm.client.impl.RequestExecutor.postRequest(RequestExecutor.java:71)
at org.camunda.bpm.client.impl.EngineClient.fetchAndLock(EngineClient.java:71)
at org.camunda.bpm.client.topic.impl.TopicSubscriptionManager.fetchAndLock(TopicSubscriptionManager.java:134)
at org.camunda.bpm.client.topic.impl.TopicSubscriptionManager.acquire(TopicSubscriptionManager.java:100)
at org.camunda.bpm.client.topic.impl.TopicSubscriptionManager.run(TopicSubscriptionManager.java:86)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: org.apache.http.NoHttpResponseException: so-bpmn-infra.onap:8081 failed to respond
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261)
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165)
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:157)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272)
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:221)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:165)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:140)
at org.camunda.bpm.client.impl.RequestExecutor.executeRequest(RequestExecutor.java:85)
... 6 common frames omitted
2020-12-28T12:07:34.947Z|2a62620a-c9d3-4d7f-8fc5-6c323d5a2a0a|org.onap.so.adapters.vnf.MsoVnfPluginAdapterImpl - inputs: item 0: vf_module_id=05aa245d-b5c1-49ae-a755-f1ae0f24c92f item 1: k8s-rb-profile-name=default item 2: vnf_id=95cccdef-7b53-49be-bfdb-386b8cb10e1d item 3: vnf_name=sInstance-nginxcnf-2-vf-1 item 4: availability_zone_0=k8saz item 5: environment_context=General_Revenue-Bearing item 6: user_directives={} item 7: workload_context=Production item 8: vf_module_name=sInstance-nginxcnf-2-vf-1-vfm-1 item 9: vf_module_index=0 item 10: sdnc_directives={ "attributes": [ {"attribute_name": "k8s-rb-profile-name", "attribute_value": "default"}, {"attribute_name": "availability_zone_0", "attribute_value": "k8saz"}] }
I think, we shall be handling this issue better:
1. If we don`t expect the external system to be present, then we shall not try to connect to it.
2. If we expect the external system to be present, we shall log a connectivity error, and not really a Java exception with a stack trace.