Issue DNS errors during ip remap cause exit 1 before web hosting can be switched

[websavers]

We've done a number of migrations from CentOS 6 to CentOS 8 (and now AlmaLinux 8) without any problems running first reconfigurator and now `plesk bin ipmanage --remap /path/to/ip_map.txt`

Today we got a bunch of DNS updating errors after a Plesk Migration which ultimately result in the ip mapping exiting prior to actually completing the IP changes to web and mail services. Note that the first line below was repeated many times for multiple domains that we migrated:

Unable to add the new2.domain.com. IN A $LIVE_IP record to zone domain.com: DNS record 'new2.domain.cp,. IN A $LIVE_IP' already exists.:
0: /usr/local/psa/admin/plib/Task/Async/Executor.php:42
Task_Async_Executor->execute()
1: /usr/local/psa/admin/plib/scripts/task-async-executor.php:6

Exit 1

To fix it we had to manually run the IP change as described here in the Plesk KB. And then update the IP in the DB for the particular domain that refused to change:

UPDATE dns_recs SET val = '$LIVE_IP' WHERE val = '$TMP_IP';

Which reported a single change, indicating that this was just *one* domain in the end that failed to update.

What I'd like to see happen: rather than exiting part way through changing IPs, if the ip map script encounters an error with a domain, it should continue the process, then report the issue with that one domain at the end. Then we can manually take action on that one domain with the problem rather than having to manually repair everything.

 

[websavers]

Just had yet another migration (after dozens without issue) where DNS records refused to update properly with ipmanage --remap. Had to run the following to fix it:

update dns_recs set host = '<CORRECT_IP>' where host = '<WRONG_IP>';
update dns_recs set displayHost = '<CORRECT_IP>' where displayHost = '<WRONG_IP>';
update dns_recs set val = '<CORRECT_IP>' where val = '<WRONG_IP>';
update dns_recs set displayVal = '<CORRECT_IP>' where displayVal = '<WRONG_IP>';

Then `plesk repair dns` to fix it.

When the IP remapping was part of the autoconfigure utility, this never happened.