Seeing a large number of these messages in SDNC logs in integration:

{{org.onap.ccsdk.sli.core.sli.SvcLogicException: Exception while posting http request to client URI is not absolute
{{ at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendHttpRequest(RestapiCallNode.java:855) ~[bundleFile:?]}}
{{ at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendRequest(RestapiCallNode.java:501) [bundleFile:?]}}
{{ at org.onap.ccsdk.sli.plugins.restapicall.RestapiCallNode.sendRequest(RestapiCallNode.java:474) [bundleFile:?]}}
{{ at jdk.internal.reflect.GeneratedMethodAccessor105.invoke(Unknown Source) ~[?:?]}}
{{ at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:?]}}}}

These messages appear to be due to an issue in the A1 policy manager.  There are no non Near-RT RICs provisioned, but A1 policy manager is still sending a message to the A1 interface in SDNC with no non Near-RT RIC IP addresses. The directed graph does not handle this correctly and, instead of ignoring this message, it constructs an illegal URL (with no host address), leading to this exception