Skip to main content

M32

 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

Popular posts from this blog

2 - Dell Open Networking Switch OS10

Managed Object Procedure (MOP) for Upgrading Dell Open Networking Switch OS10 to Latest Firmware on an Air-Gapped System Purpose: This MOP outlines the steps to upgrade the firmware on a Dell Open Networking (OS10) switch to the latest version on an air-gapped system (no internet connection). The upgrade will be performed by transferring the firmware image using Secure Copy (SCP) from a laptop directly connected to the switch's dedicated management interface. Service Impact Summary: The switch's management interface will be unavailable during the upgrade process, which can range from a few minutes to half an hour depending on the switch model and firmware size. Depending on the firmware version being upgraded from, there might be brief service interruptions on data plane ports while the switch reboots after the upgrade. Backup Procedure: Configuration Backup: Connect to the switch using the command-line interface (CLI). Enter the following command to capture the runnin...

Swagger

Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Subject: Next Steps for Troubleshooting Your Filter Issue - Test Scenario with Swagger Hi [Customer Name], Thank you for your patience as we continue to troubleshoot the filter deletion issue you're experiencing. To further investigate the cause, we'd like your help running a quick test scenario using the Swagger software. Here's what we need you to do: Access Swagger: Open Swagger for our application. You can usually access it through [link to Swagger documentation/interface - replace with specific instructions]. Target Selection: Locate the endpoint related to retrieving filters. This might be named something like "GET /filters". "Try it Out": Click the "Try it out" button associated with the endpoint. Filter Criteria: In the request body section, locate the field for filtering results. Set the criteria to retrieve only filters with an "active...

Closure

Closure Criteria: Issue Resolved : The underlying problem has been successfully resolved. Workaround Provided : A temporary solution has been provided, and the user has been informed of the permanent resolution timeline. Issue is Deferred : The customer has agreed to defer resolution to a future release or update. Additional Considerations: Knowledge Base Update : If applicable, the resolution should be documented in the knowledge base for future reference. Follow-up : If necessary, schedule a follow-up ticket to ensure the resolution is holding. Escalation : If the issue cannot be resolved, escalate to BES team.