OLVM: Disaster Recovery (DR) Mapping File Attribute Is Failed
(Doc ID 2958386.1)
Last updated on JULY 10, 2023
Applies to:
Linux OS - Version Oracle Linux 7.9 with Unbreakable Enterprise Kernel [5.4.17] and laterLinux x86-64
Information in this document applies to any platform.
Symptoms
On Oracle Linux Virtualization Manager (OLVM), generating Disaster Recovery (DR) mapping file attribute is failed. Please refer to the details below.
<snip from the error messages>
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match 'all' <==== Please refer to the keyword "localhost", it uses generic localhost instead of the engine host/manager FQDN. This is the red flag of the issue...!!!
PLAY [Setup oVirt environment] ****************************************************************************************************************************************
TASK [Gathering Facts] ************************************************************************************************************************************************
ok: [localhost]
TASK [ovirt.ovirt.disaster_recovery : Genereate mapping var file] *****************************************************************************************************
included: /usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/disaster_recovery/tasks/generate_mapping.yml for localhost <==== Please refer to the keyword "localhost", it uses the generic localhost instead of the engine host/manager FQDN. This is the red flag of the issue...!!!
TASK [ovirt.ovirt.disaster_recovery : Generate mapping var file] ******************************************************************************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": ["python3", "/usr/share/ansible/collections/ansible_collections/ovirt/ovirt/roles/disaster_recovery/files/generate_mapping.py", "-a", "https://xxx.xxx.xxx.xxx/ovirt-engine/api", "-u", "admin@internal", "-p", "xxxxxx", "-c", "/etc/pki/ovirt-engine/ca.pem", "-f", "disaster_recovery_vars.yml"], "delta": "0:00:00.170017", "end": "2023-06-28 17:59:40.158344", "msg": "non-zero return code", "rc": 1, "start": "2023-06-28 17:59:39.988327", "stderr": "Traceback (most recent call last):\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 382, in authenticate\n self._sso_token = self._get_access_token()\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 617, in _get_access_token\n sso_response = self._get_sso_response(self._sso_url, post_data)\n File \"/usr/lib64/python3.6/site-packages/ovirtsdk4/__init__.py\", line 694, in _get_sso_response\n curl.perf
<=== Please refer to the OLVM Admin Portal (https://xxx.xxx.xxx.xxx/ovirt-engine/api), it uses IP address instead of the engine host/manager FQDN. This is another red flag of the issue...!!!
Changes
Deployment of Oracle Linux Virtualization Manager (OLVM) Disaster Recovery (DR).
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |