Nethvoice: Report filters missing due to hostname resolution in reports-api container

[Amygos]

Introduction
After each NethVoice update or scheduled nightly sync, report filters are missing in the dashboard and must be restored manually. The error message "filter values not present in cache" appears, and API calls to retrieve filters return 404 errors. This has been observed on multiple instances and requires manual intervention every time.

Steps to reproduce:

1. Update NethVoice or wait for nightly sync script execution on the affected NS8 instance.
2. Access the report dashboard.
3. Observe missing data and error messages regarding filter cache.
4. Restore filters manually using:
   • podman exec -it reports-api /usr/bin/tasks values
   • podman exec -it reports-api /usr/bin/tasks phonebook

Expected behavior:
Report filters should always be available after updates or scheduled tasks, without manual intervention.

Actual behavior:
Filters disappear after updates or nightly sync. API calls to /pbx-report-api/filters and /pbx-report-api/filters/trunks fail with 404. Console logs repeatedly show {message: 'filter values not present in cache', status: 'redis: nil'}. Manual commands are required to restore functionality.

Components:

• ns8-nethvoice

See also:
Related tickets:

• https://helpdesk.nethesis.it/a/tickets/191294
• https://helpdesk.nethesis.it/a/tickets/191349
• https://helpdesk.nethesis.it/a/tickets/191718
• https://helpdesk.nethesis.it/a/tickets/191852
  Mattermost discussion: https://mattermost.nethesis.it/nethesis/pl/p6dzbsiqm7nbpnicsmej6tu1se

[Amygos]

Testing release nethesis/ns8-nethvoice 1.4.2-testing.7

[Amygos]

Test Case 1: Validate Report Filters Availability After Nightly Sync Task

• Objective: Ensure report filters are present after the execution of the nightly sync script, without manual restoration.
• Preconditions:
  • The ns8-nethvoice module is installed from the testing version with the PR fix.
• Steps:
  1. Trigger the nightly sync task manually or wait for its scheduled execution.
  2. After task completion, access the NethVoice dashboard.
  3. Navigate to the reports section.
  4. Check the availability of report filters.
  5. Verify API endpoints /pbx-report-api/filters and /pbx-report-api/filters/trunks respond appropriately.
  6. Inspect logs for errors related to filter cache or hostname resolution.
• Expected Results:
  • Report filters remain present and functional after sync.
  • API endpoints return valid filter data.
  • No cache or hostname resolution errors are logged.

---

Test Case 2: Validate Hostname Resolution Inside reports-api Container

• Objective: Confirm that the NETHVOICE_HOST is correctly resolved inside the reports-api container using --add-host.
• Preconditions:
  • The ns8-nethvoice module is installed from the testing version.
• Steps:
  1. Access the reports-api container.
  2. Inside the container, run network tools (e.g., ping, nslookup) for NETHVOICE_HOST.
  3. Check that NETHVOICE_HOST resolves to the correct IP.
  4. Confirm that internal API connections relying on NETHVOICE_HOST work as intended.
• Expected Results:
  • NETHVOICE_HOST resolves correctly within the container.
  • No connection errors related to NETHVOICE_HOST are present.

[viktec]

Test Case 1 : ok

Test Case 2 : ok

[nethvoice1@rl1 state]$ podman exec -it reports-api ash
/ # ping $NETHVOICE_HOST
PING voicevr.demo.neth.eu (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: seq=0 ttl=42 time=0.096 ms
64 bytes from 127.0.0.1: seq=1 ttl=42 time=0.109 ms
64 bytes from 127.0.0.1: seq=2 ttl=42 time=0.142 ms
^C
--- voicevr.demo.neth.eu ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.096/0.115/0.142 ms