I have to correct myself,
also the AAF services have the same problems, e.g. aaf-sms-preload:
Waiting for SMS to accept requests...
Get https://aaf-sms.onap:10443/v1/sms/quorum/status: dial tcp
10.233.57.27:10443: connect: connection refused
Waiting for SMS to accept requests...
Get https://aaf-s
Hi again,
with my patch so far the AAF component is up and running.
But the clients using the cert-initializer (e.g. SO, SDC, CDS) still fail.
The aaf-config container logs show valid certificates:
Validate Configuration and Certificate with live call
2023-09-19T13:41:50.219+ INIT [cadi]