Re: aaf-sms met issue x509: certificate has expired or is not yet valid #aaf
Make sure you clean up the dockerdata-nfs area for aaf-sms before redeploying. It looks like it is using things from a previous deployment.
-- K i r a n
From: onap-discuss@... [mailto:onap-discuss@...] On Behalf Of wutianwei
Sent: Wednesday, June 12, 2019 11:48 PM
To: Kamineni, Kiran K <kiran.k.kamineni@...>
Subject: Re: [onap-discuss] aaf-sms met issue x509: certificate has expired or is not yet valid #aaf
I follow the step and update the certs https://jira.onap.org/browse/AAF-848
But the aaf-sms still fail.
When I check the log of aaf-sms-preload I got the result
“Waiting for SMS to accept requests…”
Then I check the log of aaf-sms pod, I get result:
I also check the aaf-sms-vault container of aaf-sms-valut-0 pod. Here is the logs:
Do you have any idea about it?
You can follow the instructions here to update hte certs in the old image:
-- K i r a n
On Behalf Of wutianwei
I deployed the Casablanca ONAP with oom. But health check for aaf sms failed.
I found someone has the same issue.
It seems that certificate for aaf-sms expired, as some people point out.
Kiran Kamineni has submitted a patch to updated certificates for SMS, it works for master.
After I changed the aaf-sms docker image version to 4.0.1 from 3.0.1, aaf sms still failed. I think this is because I deployed Casablanca.
So could anyone help me out