OLVM: Self-Hosted Engine Setup Error "Please Check That The Device Is Empty" (Doc ID 2677797.1)

Last updated on MARCH 23, 2022

Applies to:

Symptoms

During Self-Hosted Engine setup, the hosted-engine --deploy reports below error:

[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Physical device initialization failed. Please check that the device is empty and accessible by the host.]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault deta il is \"[Physical device initialization failed. Please check that the device is empty and accessible by the host.]\" . HTTP response code is 400."}
[ ERROR ] Error: Fault reason is "Operation Failed". Fault detail is "[Physical device initialization failed. Please check that the device is empty and accessible by the host.]". HTTP response code is 400.
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "Fault reason is \"Operation Failed\". Fault deta il is \"[Physical device initialization failed. Please check that the device is empty and accessible by the host.]\" . HTTP response code is 400."}

ovirt-hosted-engine-setup-xxxxxxxxxxx.log reported below error:

please check the logs for the issue, fix accordingly or re-deploy from scratch.
2020-06-05 00:28:46,544-0400 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-xxxxxxxxxxx.log

2020-06-05 00:28:46,544-0400 ERROR otopi.plugins.gr_he_common.core.misc misc._terminate:167 Hosted Engine deployment failed: please check the logs for the issue, fix accordingly or re-deploy from scratch.
2020-06-05 00:28:46,544-0400 DEBUG otopi.plugins.otopi.dialog.human dialog.__logString:204 DIALOG:SEND Log file is located at /var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-xxxxxxxxxxx.log

ovirt-hosted-engine-setup-ansible-create_target_xxxxxxxxxxx.log:

2020-06-05 00:28:04,316-0400 ERROR ansible failed {'status': 'FAILED', 'ansible_type': 'task', 'ansible_task': u'Inject netwo
rk configuration with guestfish', 'ansible_result': u"type: <type 'dict'>\nstr: {'stderr_lines': [u'guestfish: no operating s
ystem was found on this disk', u'', u'If using guestfish \\u2018-i\\u2019 option, remove this option and instead', u'use the
commands \\u2018run\\u2019 followed by \\u2018list-filesystems\\u2019.', u'You can then mount filesystems you want by hand us
ing the', u", 'task_duration': 5, 'ansible_host': u'localhost', 'ansible_playbook': u'/usr/share/ovirt-hosted-engine-setup/an
sible/trigger_role.yml'}
2020-06-05 00:28:04,316-0400 DEBUG ansible on_any args <ansible.executor.task_result.TaskResult object at 0x7f40c3b01e90> kwa
rgs ignore_errors:None
2020-06-05 00:28:04,319-0400 INFO ansible stats {
"ansible_playbook": "/usr/share/ovirt-hosted-engine-setup/ansible/trigger_role.yml",
"ansible_playbook_duration": "04:35 Minutes",
"ansible_result": "type: <type 'dict'>\nstr: {u'localhost': {'ignored': 0, 'skipped': 11, 'ok': 105, 'failures': 1, 'unre
achable': 0, 'rescued': 0, 'changed': 34}}",
"ansible_type": "finish",
"status": "FAILED"
}

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.