Description of problem: Engine setup got stuck on the appliance. Failed to execute stage 'Closing up': Engine setup is stalled on the appliance since 1800 seconds ago. Please check its log on the appliance. Hosted Engine deployment failed: this system is not reliable, please check the issue,fix and redeploy Looks like its storage or network related issue: Feb 14 15:06:26 alma04 journal: Failed to release lock: Stale file handle Feb 14 15:06:26 alma04 sanlock[25193]: 2017-02-14 15:06:26+0200 79860 [25197]: r4 write_host_block host_id 1 flags 0 gen 0 rv -116 Feb 14 15:06:26 alma04 journal: Unable to release lease on HostedEngine 116 is #define ESTALE 116 /* Stale NFS file handle */ Version-Release number of selected component (if applicable): rhvm-appliance-4.1.20170126.0-1.el7ev.noarch sanlock-3.4.0-1.el7.x86_64 ovirt-node-ng-nodectl-4.1.0-0.20170104.1.el7.noarch qemu-kvm-rhev-2.6.0-28.el7_3.3.x86_64 vdsm-4.19.4-1.el7ev.x86_64 ovirt-imageio-common-1.0.0-0.el7ev.noarch ovirt-engine-sdk-python-3.6.9.1-1.el7ev.noarch ovirt-setup-lib-1.1.0-1.el7ev.noarch ovirt-vmconsole-host-1.0.4-1.el7ev.noarch mom-0.5.8-1.el7ev.noarch ovirt-imageio-daemon-1.0.0-0.el7ev.noarch ovirt-hosted-engine-ha-2.1.0.1-1.el7ev.noarch ovirt-hosted-engine-setup-2.1.0.1-1.el7ev.noarch ovirt-vmconsole-1.0.4-1.el7ev.noarch libvirt-client-2.0.0-10.el7_3.4.x86_64 ovirt-host-deploy-1.6.0-1.el7ev.noarch Linux version 3.10.0-514.6.1.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Sat Dec 10 11:15:38 EST 2016 Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Sat Dec 10 11:15:38 EST 2016 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux release 7.3 How reproducible: Steps to Reproduce: 1.Deploy HE over NFS from RHEVH4.1's cockpit. 2. 3. Actual results: Deployment failed. Expected results: Deployment should pass. Additional info: Sosreport from host being attached. Unfortunately I could not collect logs from the engine as it was not reachable.
Created attachment 1250271 [details] sosreport-localhost.localdomain-20170214155318.tar.xz
This is a known issue, we're working on it. *** This bug has been marked as a duplicate of bug 1421249 ***