Description of problem: /usr/share/ovirt-hosted-engine-setup/ansible/bootstrap_local_vm.yml includes dmidecode, but dmidecode is an x86 standard, and is only available on those architectures. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.32-1.el7.noarch How reproducible: run on the ppc64le linux: hosted-engine --deploy Steps to Reproduce: 1.hosted-engine --deploy #on the centos 7.5 ppc64le 2. 3. Actual results: Expected results: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": true, "cmd": "if [ -e /etc/vdsm/vdsm.id ]; then cat /etc/vdsm/vd sm.id; else dmidecode -s system-uuid; fi;", "delta": "0:00:00.004206", "end": "2018-11-29 14:20:13.506326", "msg": "n on-zero return code", "rc": 127, "start": "2018-11-29 14:20:13.502120", "stderr": "/bin/sh: dmidecode: command not fo und", "stderr_lines": ["/bin/sh: dmidecode: command not found"], "stdout": "", "stdout_lines": []} Additional info: For example, please look how it's done in /usr/share/ovirt-host-deploy/plugins/ovirt-host-deploy/vdsm/vdsmid.py
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Reporter, can you please help verifying https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/pull/108 on ppc64le?
ovirt-ansible-hosted-engine-setup is for 4.3. There is no appliance fit to PPC arch in 4.3, the deployment fails on that step (before the bootstrap task) - dependency issue with ovirt-hosted-engine-setup. I can't verify that we pass this step, in 4.2 there is no ovirt-ansible-hosted-engine-setup with the fix. I can tell that in: ovirt-hosted-engine-setup-2.3.6-1.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.12-1.el7ev.noarch in /usr/share/ansible/roles/ovirt.hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml - name: Get host unique id shell: | if [ -e /etc/vdsm/vdsm.id ]; then cat /etc/vdsm/vdsm.id; elif [ -e /proc/device-tree/system-id ]; then cat /proc/device-tree/system-id; #ppc64le else dmidecode -s system-uuid; fi; Downloading manually ovirt-ansible-hosted-engine-setup in 4.2 gives: ovirt-ansible-hosted-engine-setup-1.0.7-2.el7ev.noarch Without the fix. Sandro, is it enough from your side to verify by having the fix code inside? If not, how shall we proceed with the deployment?
(In reply to Liran Rotenberg from comment #3) > Sandro, is it enough from your side to verify by having the fix code inside? > If not, how shall we proceed with the deployment? It's enough, we don't have a ppc64le appliance so no real point in going further. Moving to verified.
This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.