NethVoice: Backend support for new certificate management UX (failures & Traefik restart warning)

[Amygos]

Proposed Feature
Comply NethVoice backend with new UX requirements for certificate management: inform cluster-admin of certificate failures and show Traefik restart warnings, as required by NS8 guidelines.

Purpose and Motivation
To improve admin clarity and consistency across NS8, NethVoice backend must handle and communicate Let's Encrypt certificate validation failures, and alert the user if a Traefik restart is needed (e.g., after certificate cleanup). This ensures a seamless, compliant UX and reduces troubleshooting.

Proposed Solution

• Modify configure-module action to call set-route with lets_encrypt_check:true for backend ACME error validation.
• Adjust get-configuration to track the state of the new flag.
• Ensure the system can signal UI about validation errors and restarts, following the NS8 certificate management guides.

Alternative Solutions

• Keep current implementation (do not report failures/warnings). Not recommended, as it diverges from platform UX updates.

Additional Context

• Related: Parent issue #7670

[Amygos]

Test Case 1: Fresh Installation of NethVoice

• Preconditions: Clean NethServer 8 system.
• Actions:
  1. Install the NethVoice module following the documented procedure.
  2. Complete the initial configuration wizard.
• Expected Results:
  • The module installs without errors.
  • The UI is accessible.
  • Certificate options are presented correctly.

Test Case 2: Upgrade from Previous NethVoice

• Preconditions: System running a previous version of NethVoice.
• Actions:
  1. Upgrade the module to the tesdting version.
  2. Check if all prior configurations persist.
• Expected Results:
  • Upgrade process completes with no errors.
  • Previous settings, extensions, and certificate states are preserved and visible.

Test Case 3: Set Up Valid DNS Records

• Preconditions: Valid public DNS records for the NethVoice application
• Actions:
  1. Configure the pbx ans cti FQDNs in the module to match the public DNS records.
  2. Use the toggle to request a Let's Encrypt certificate.
  3. Apply the configuration.
• Expected Results:
  • DNS validation passes.
  • Let's Encrypt certificate is successfully issued and listed in the NS8 UI.
  • NethVoice service is reachable from the public domain.

Test Case 4: Set Up Invalid DNS Record

• Preconditions: No valid public DNS for the chosen domain (e.g., cti.example.com).
• Actions:
  1. Configure the server FQDN to cti.example.com in the module.
  2. Request a Let's Encrypt certificate.
• Expected Results:
  • Certificate request fails gracefully, displaying a clear error about DNS validation.
  • No certificate is installed.
  • The logs accurately report the error.

Test Case 5: Toggle Off on Domain with Existing Certificate

• Preconditions: Valid DNS, Let's Encrypt certificate present for the domains.
• Actions:
  1. Use the UI to toggle off the Let's Encrypt management for the domains.
  2. Check the "Certificates Management" section of NS8 UI.
• Expected Results:
  • The certificates are removed from the Certificates Management list in NS8 UI.
  • Domain reverts to non-managed certificate state or default self-signed certificate.

Test Case 6: Migration Path Validation

• Preconditions:
  • Existing NethServer 7 system with NethVoice configured.
  • NethServer 8 system ready.
  • nethserver-ns8-migration RPM from the testing repository is installed.
  • Follow Let's Encrypt migration steps.
• Actions:
  1. Trigger the migration process from NS7 to NS8, referencing the new documentation for Let's Encrypt handling.
  2. Ensure the DNS and certificate process matches instructions.
  3. Post-migration, verify:
     • The target DNS record is valid and points to the new server.
     • Let's Encrypt certificate is correctly issued.
• Expected Results:
  • Migration completes without error.
  • Certificate status is reflected accurately in NS8 UI.

[Amygos]

Testing release nethesis/ns8-nethvoice 1.5.1-testing.22