Backup Samba repo validation #7382
Description
Windows Share backup repository does not detect host name misconfiguration: its FQDN can be resolved differently by cluster nodes and lead to unexpected Restic run failure.
Steps to reproduce
- Configure a Windows file server on node A (the leader) with, with FQDN
anode.domain.test - Configure a Windows share backup repository pointing to
anode.domain.test - Run the backup of an application in the worker node.
Actual result
Samba repository validation succeedes, but worker nodes cannot reach the backup repo share and Restic run fails.
Expected result
Validation fails during backup configuration. We add a probe also when a module is configured to use the backup repo: with this strategy DNS issues should be caught before Restic runs.
Additional information
The leader-side validator leads to issues also if the worker node can theoretically reach anode.domain.test, but the leader validation procedure fails, preventing a successful configuration to succeed. So the bug must be fixed for both cases
See also
Private channel chat https://mattermost.nethesis.it/nethesis/pl/3rpeetk1sbfcxx63opraygo3za
Thanks to @nrauso @lucagasparini