Description of problem: ------------------------------ After user creates a VM out of template and runs it the VM is going to paused state with storage I/O storage error and later investigating the logs found an error stating " stale file handler ". Version-Release number of selected component: ---------------------------------------------- glusterfs-server-3.12.2-47.el7rhgs.x86_64 gluster-ansible-cluster-1.0-1.el7rhgs.noarch gluster-ansible-repositories-1.0-1.el7rhgs.noarch gluster-ansible-features-1.0.4-5.el7rhgs.noarch gluster-ansible-infra-1.0.3-3.el7rhgs.noarch gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch gluster-ansible-roles-1.0.4-4.el7rhgs.noarch Red Hat Enterprise Linux Server release 7.6 (Maipo) How reproducible: ------------------- 2/2 Steps to Reproduce: --------------------- 1.Successful deploy gluster and hosted engine. 2.Create RHEL 7.6 template and then create vm out of it . 3.The VM goes to pause state after user runs the VM. Actual results: ---------------------- VM goes to pause state with storage I/O error. Expected results: ---------------------- VM should not go in pause state
Status?
Being RC'ed in Bug 1700319
Created attachment 1557150 [details] vm store.log
I could reproduce this issue with RHV 4.3.5 + RHEL 7.7 + RHGS 3.5.0 ( glusterfs-6.0-5 ) with the following steps: 1. Create a RHEL 7.6 VM with 40GB boot disk, preallocated( using falloc ) - all this is done with VM creation workflow in RHV 2. Post OS installation, powered off the VM and created a template of the VM 3. Created 10 VM out of the template 4. Started these VMs altogether. One of the VM paused
As per dependent bug - fixed in ovirt-engine-4.3.5.3
Tested with RHV 4.3.8 with RHGS 3.5.1 ( glusterfs-6.0-25.el7rhgs ) 1. Deployed RHHI-V with 3 nodes, with gluster storage domains backed with replica 3 gluster volume 2. Created RHEL 7.7 VM and created template out of it. 3. Create 15 VMs out of this template ( VMs are created as 'Clone', where the template image is copied to new VM ) 4. Started all the VM at the sametime None of the VMs are going paused
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0508