Re-deploying ovirt engine fails after renaming HE storage domain

[IOMadness]

Trying this w/ oVirt Node 4.5.4.

Describe the bug

I'm trying to redeploy a hosted engine backup I made to test migrating the HE over to a new storage domain. However, after the script updates the previous HE storage domain name, it tries to save the value of DisableFenceAtStartup and fails as it seems unable to talk to the database.

To reproduce

Put an existing oVirt cluster into global maintenance mode.
Stop the hosted engine
Create a backup of the HE, move to a remote location.
Reinstall a fresh copy of oVirt Node 4.5.4 on the prior HE host.
Redeploy the hosted engine from backup w/ "hosted-engine --deploy --restore-from-backup= --4
Answer questions for the re-deployment, set datacenter and cluster name to same as the backed up HE, as well as HE IP.

Expected behavior

Expect the script to re-deploy the HE from the backup to its prior state.

Screenshots

Additional context

Our overarching goal is to migrate an existing HE in a production environment to a new storage domain without upsetting existing VMs running our services so that we can make changes to our primary VM and HE storage.

[IOMadness]

This is where it fails in the hosted-engine output log:
2023-07-05 16:02:40,778-0600 INFO otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:115 TASK [ovirt.ovirt.hosted_engine_setup : Save original DisableFenceAtStartupInSec]
2023-07-05 16:02:42,882-0600 DEBUG otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:109 {'changed': True, 'stdout': '', 'stderr': 'Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false', 'rc': 1, 'cmd': "set -euo pipefail && engine-config -g DisableFenceAtStartupInSec | cut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", 'start': '2023-07-05 16:02:41.209391', 'end': '2023-07-05 16:02:42.641490', 'delta': '0:00:01.432099', 'msg': 'non-zero return code', 'invocation': {'module_args': {'_raw_params': "set -euo pipefail && engine-config -g DisableFenceAtStartupInSec | cut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", '_uses_shell': True, 'stdin_add_newline': True, 'strip_empty_ends': True, 'argv': None, 'chdir': None, 'executable': None, 'creates': None, 'removes': None, 'stdin': None}}, 'stdout_lines': [], 'stderr_lines': ['Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false'], '_ansible_no_log': None, '_ansible_delegated_vars': {'ansible_host': '192.168.1.252', 'ansible_port': None, 'ansible_user': 'root', 'ansible_connection': 'smart'}}
2023-07-05 16:02:42,982-0600 ERROR otopi.ovirt_hosted_engine_setup.ansible_utils ansible_utils._process_output:113 fatal: [localhost -> 192.168.1.252]: FAILED! => {"changed": true, "cmd": "set -euo pipefail && engine-config -g DisableFenceAtStartupInSec | cut -d' ' -f2 > /root/DisableFenceAtStartupInSec.txt", "delta": "0:00:01.432099", "end": "2023-07-05 16:02:42.641490", "msg": "non-zero return code", "rc": 1, "start": "2023-07-05 16:02:41.209391", "stderr": "Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false", "stderr_lines": ["Picked up JAVA_TOOL_OPTIONS: -Dcom.redhat.fips=false"], "stdout": "", "stdout_lines": []}