MAAS API retries and timeout for DNSHA are not customizable

[Vladimir Grevtsev]

There is a python script in hacluster charm, which invokes a MAAS API on the DNS endpoint change event from the Pacemaker:

charm-hacluster git:(master*) $ grep -RiP 'binfile='
files/ocf/maas/dns:binfile="${HA_BIN}/maas_dns.py"

charm-hacluster git:(master*) $ grep -RiP 'add_argument' files/ocf/maas/maas_dns.py
    parser.add_argument('--maas_server', '-s',
    parser.add_argument('--maas_credentials', '-c',
    parser.add_argument('--fqdn', '-d',
    parser.add_argument('--ip_address', '-i',
    parser.add_argument('--ttl', '-t',
    parser.add_argument('--logfile', '-l',
    parser.add_argument('--maas_api_retries', '-r',
    parser.add_argument('--maas_base_delay', '-b',
    parser.add_argument('--maas_retry_codes', '-x',

charm-hacluster git:(master*) $ grep -RiP 'python3 \$binfile'
files/ocf/maas/dns: cmd="python3 $binfile --fqdn=$OCF_RESKEY_fqdn --ip_address=$myipaddr --maas_server=$OCF_RESKEY_maas_url --maas_credentials=$OCF_RESKEY_maas_credentials "

As we could see from the above output, this script has an option to adjust the timeout - however, a non-default parameter is never passed through to the CLI in "files/ocf/maas/dns" script. Thus, the MAAS API retries count and timeout can never be configured.