Created attachment 1373162 [details] vdsm.log Description of problem: hosted-engine --deploy failed. the reason for this failure revealed on this patch: https://gerrit.ovirt.org/#/c/85018/ in the patch, vdsm user checks the file descriptor of seed.iso which doesn't have permission for the folder containing seed.iso Need to add permission for this directory How reproducible: 100% Steps to Reproduce: 1. hosted-engine --deploy Actual results: failed to deploy Expected results: deployment finish successfuly Additional info: Logs attached.
Please provide more detailed reproduction steps.
Nikolai, This was reproducible easily before merging the patch by doing hosted-engine --deploy --noansible If you want to reproduce the bug again and see the error, simply revert my patch locally and run 'hosted-engine --deploy --noansible'. IMO, it's unnecessary, just do a deployment to see everything is working fine.
(In reply to Ido Rosenzwig from comment #2) > Nikolai, > This was reproducible easily before merging the patch by doing hosted-engine > --deploy --noansible > > If you want to reproduce the bug again and see the error, simply revert my > patch locally and run 'hosted-engine --deploy --noansible'. > IMO, it's unnecessary, just do a deployment to see everything is working > fine. Yes, but what ere the reproduction exact steps? Deployment of SHE done on host without any ISO, then deployment itself is downloading rpm with the appliance, then what?
There are no special exact steps for the reproduction of the bug other then deploying hosted-engine by doing 'hosted-engine --deploy --noansible' with default answers, specially generated cloud-init file.
Successfully deployed using default answers including cloud-init generation, deployed over Gluster storage domain. Works for me on these components: ovirt-hosted-engine-ha-2.2.4-1.el7ev.noarch ovirt-hosted-engine-setup-2.2.9-1.el7ev.noarch rhvm-appliance-4.2-20180202.0.el7.noarch Linux 3.10.0-693.17.1.el7.x86_64 #1 SMP Sun Jan 14 10:36:03 EST 2018 x86_64 x86_64 x86_64 GNU/Linux Moving to verified.
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.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.