Comment 4 for bug 1988347

I don't see how this error could be a cause for the failure of this job.

The code that is being executed is here:

https://opendev.org/x/tripleo-ipa/src/branch/master/tripleo_ipa/roles/tripleo_ipa_dns/tasks/dns.yaml#L50-L78

Essentially, the code attempts to modify the existing DNS entries, and if that fails, then in the rescue section adds the required entry.

We see this in the logs.

2022-08-31 18:42:18 | 2022-08-31 18:42:18.080724 | fa163edd-246c-3638-fe65-000000005895 | TIMING | tripleo_ipa_dns : set record type | undercloud | 0:14:39.445888 | 0.04s
2022-08-31 18:42:18 | 2022-08-31 18:42:18.089570 | fa163edd-246c-3638-fe65-000000005896 | TASK | add dns zone
2022-08-31 18:42:18 | 2022-08-31 18:42:18.929152 | fa163edd-246c-3638-fe65-000000005896 | OK | add dns zone | undercloud
2022-08-31 18:42:18 | 2022-08-31 18:42:18.931318 | fa163edd-246c-3638-fe65-000000005896 | TIMING | tripleo_ipa_dns : add dns zone | undercloud | 0:14:40.296473 | 0.84s
2022-08-31 18:42:18 | 2022-08-31 18:42:18.943993 | fa163edd-246c-3638-fe65-000000005898 | TASK | try modifying forward dns record
2022-08-31 18:42:19 | 2022-08-31 18:42:19.889906 | fa163edd-246c-3638-fe65-000000005898 | FATAL | try modifying forward dns record | undercloud | error={"changed": false, "msg": "`arecord` not found."}
2022-08-31 18:42:19 | 2022-08-31 18:42:19.891074 | fa163edd-246c-3638-fe65-000000005898 | TIMING | tripleo_ipa_dns : try modifying forward dns record | undercloud | 0:14:41.256232 | 0.95s
2022-08-31 18:42:19 | 2022-08-31 18:42:19.903305 | fa163edd-246c-3638-fe65-00000000589a | TASK | add forward dns record
2022-08-31 18:42:20 | 2022-08-31 18:42:20.806253 | fa163edd-246c-3638-fe65-00000000589a | CHANGED | add forward dns record | undercloud
2022-08-31 18:42:20 | 2022-08-31 18:42:20.807581 | fa163edd-246c-3638-fe65-00000000589a | TIMING | tripleo_ipa_dns : add forward dns record | undercloud | 0:14:42.172740 | 0.90s

Note that the execution does not halt. Rather it fails later on trying to set up mysql - which of course, causes a bunch of other stuff to fail.

I think this error is a red herring -- unless it points to some underlying change in DNS that may be causing the real failure.