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 it orphaned within the Pending Delete queue.
This information has been forwarded to our development team for a bug fix. We will continue to monitor their progress and provide updates as they become available. And overall the Module recognising the Invalid Filter, responding with the correct Feedback Code, and the main dashboard showing inactive filters in Grafana, appears to be behaving as expected. The Delete then causes the “stuck” intercept to remain in the system.
I will continue to closely track the development team's progress on the issue and keep you informed of any significant developments. Please do not hesitate to reach out if you have any further questions or require additional information.
Thank you for your patience and understanding.
Comments
Post a Comment