Creole House Weight Management Journey

  Subject: Update on Pending Delete Intereps and Grafana Issue – Good Day.  Just wanted to send a quick update on the Invalid Interceptions "stuck" in Pending Delete. We worked with our colleague to successfully reproduce the scenario in our internal Reference environment.  The issue is that an Invalid formatted Interception can sometimes be accepted by the TSS (using Curl or Swagger). This is passed through the TSS > Filter Provider TSS, and distributed to the Modules. By the time that gets to the ETSI X1/X23 modules, they correctly identify the Invalid Filter Criterion and respond with 30002 Invalid Criterion Feedback Code. At this point, the intercept will sit in Interceptions Not Active, which can also seen in Grafana on the Inactive Filters (main) dashboard, and when using the GET Target Feedbacks by Filter ID. Upon attempting to DELETE the Invalid Intercept, the module is then unable to delete the invalid interception without a restart of the module, thus leaving...

  If customer is saying all the certs are showing the correct ones, maybe the error message is valid.  And based on this page   http://curl.haxx.se/docs/sslcerts.html , which is outlined in the error message, maybe the cert used with curl is out of sync.  (i.e. If curl was built with Schannel or Secure Transport support, then curl uses the system native CA store for verification . All other TLS libraries use a file based CA store by default. )   A process of copying your certificates inside /etc/pki/ca-trust/source/anchors/ then running the following command “update-ca-trust”, may help the issue along.    We don’t have access to prod so I did a comparison in lab and the certis in /etc/pki/ca-trust/source/anchors/ seem to be updated and it doesn’t get the error.    Some things researched or to check on prod maybe: not sure if it was done already but following the error message….. The error seems to say it has accessed the NSS ...