Created attachment 1359541 [details] logs from alma03 Description of problem: Deployment of SHE stuck on "Stage: Misc configuration" and then after long timeout deployment fails with: [ ERROR ] Engine setup got stuck on the appliance [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled on the appliance since 1800 seconds ago. Please check its log on the appliance. Looks like this is the issue: 2017-11-27 17:36:28,256+0200 INFO (jsonrpc/7) [vdsm.api] FINISH prepareImage error=Volume does not exist: (u'24e0ccff -f029-4b23-930b-ecb85ab11924',) from=::1,43820, task_id=be70e5cd-4dc8-4166-8373-07581905b1d1 (api:50) 2017-11-27 17:36:28,257+0200 ERROR (jsonrpc/7) [storage.TaskManager.Task] (Task='be70e5cd-4dc8-4166-8373-07581905b1d1' ) Unexpected error (task:875) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 882, in _run return fn(*args, **kargs) File "<string>", line 2, in prepareImage File "/usr/lib/python2.7/site-packages/vdsm/common/api.py", line 48, in method ret = func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/storage/hsm.py", line 3157, in prepareImage raise se.VolumeDoesNotExist(leafUUID) VolumeDoesNotExist: Volume does not exist: (u'24e0ccff-f029-4b23-930b-ecb85ab11924',) 2017-11-27 17:36:28,257+0200 INFO (jsonrpc/7) [storage.TaskManager.Task] (Task='be70e5cd-4dc8-4166-8373-07581905b1d1' ) aborting: Task is aborted: "Volume does not exist: (u'24e0ccff-f029-4b23-930b-ecb85ab11924',)" - code 201 (task:1181 ) 2017-11-27 17:36:28,258+0200 ERROR (jsonrpc/7) [storage.Dispatcher] FINISH prepareImage error=Volume does not exist: ( u'24e0ccff-f029-4b23-930b-ecb85ab11924',) (dispatcher:82) 2017-11-27 17:36:28,258+0200 INFO (jsonrpc/7) [jsonrpc.JsonRpcServer] RPC call Image.prepare failed (error 201) in 0. 01 seconds (__init__:573) Host alma03 has gluster volume mounted as follows: gluster01.scl.lab.tlv.redhat.com:/nsednev_he_1 on /rhev/data-center/mnt/glusterSD/gluster01.scl.lab.tlv.redhat.com:_nsednev__he__1 type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-2.2.0-0.0.master.20171124110627.gitc5547b6.el7.centos.noarch ovirt-hosted-engine-ha-2.2.0-0.0.master.20171122155227.20171122155225.gitbc3ec09.el7.centos.noarch ovirt-engine-appliance-4.2-20171126.1.el7.centos.noarch How reproducible: 100% Steps to Reproduce: 1.Deploy SHE over Gluster volume. Actual results: Deployment getting stuck. Expected results: Deployment should be successful. Additional info: logs from host attached.
Deployment details available from here: http://pastebin.test.redhat.com/535404
(In reply to Nikolai Sednev from comment #0) > Description of problem: > Deployment of SHE stuck on "Stage: Misc configuration" and then after long > timeout deployment fails with: > [ ERROR ] Engine setup got stuck on the appliance We need engine-setup logs to check what happened there > [ ERROR ] Failed to execute stage 'Closing up': Engine setup is stalled on > the appliance since 1800 seconds ago. > Please check its log on the appliance. > > > Looks like this is the issue: > VolumeDoesNotExist: Volume does not exist: > (u'24e0ccff-f029-4b23-930b-ecb85ab11924',) This is a false positive: hosted-engine-setup is just checking for volume existence before creating it
I've tried to get in to the engine, it was alive, but I could not log in to it.
(In reply to Simone Tiraboschi from comment #2) > We need engine-setup logs to check what happened there It seams still SELinux related
The same failure happens also over NFS deployment, thus making this bug not storage type specific.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
*** Bug 1518850 has been marked as a duplicate of this bug. ***
*** Bug 1522641 has been marked as a duplicate of this bug. ***
Deployed on RHEL7.4 hosts, using: ovirt-hosted-engine-ha-2.2.0-0.0.master.20171128125909.20171128125907.gitfa5daa6.el7.centos.noarch ovirt-hosted-engine-setup-2.2.0-0.0.master.20171129192644.git440040c.el7.centos.noarch ovirt-engine-appliance-4.2-20171129.1.el7.centos.noarch Over Gluster - passed; Over NFS - passed; Over iSCSI - passed; Moving to verified.
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.
*** Bug 1540123 has been marked as a duplicate of this bug. ***