Bug 1853192

Summary: VM with disk on iscsi on PPC environment fails to start on host - Exit message: Wake up from hibernation failed:internal error: child reported (status=125): unable to set security context
Product: [oVirt] ovirt-engine Reporter: Evelina Shames <eshames>
Component: BLL.StorageAssignee: Tal Nisan <tnisan>
Status: CLOSED DUPLICATE QA Contact: Avihai <aefrat>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4.1.5CC: bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-02 07:23:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
loga none

Description Evelina Shames 2020-07-02 06:58:18 UTC 
Created attachment 1699598 [details]
loga

Description of problem:
VM with disk on iscsi on PPC environment fails to start on host with the following errors:

Engine.log:
2020-07-02 09:18:50,521+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-17) [14c64a7d] EVENT_ID: VM_DOWN_ERROR(119), VM vm_TestCase5138_0209130682 is down with error. Exit message: Wake up from hibernation failed:internal error: child reported (status=125): unable to set security context 'system_u:object_r:virt_content_t:s0' on '/rhev/data-center/mnt/blockSD/97370c99-3549-4686-8536-d067f82e5daf/images/1bc19190-6f96-4d7e-9db3-a25c87451aaa/f5dd8cc0-7491-4574-a066-00ffcc0382fb': No such file or directory.
2020-07-02 09:18:50,527+03 ERROR [org.ovirt.engine.core.vdsbroker.monitoring.VmsMonitoring] (ForkJoinPool-1-worker-17) [14c64a7d] Rerun VM 'ad70f664-cf00-4390-a8dc-ccb267dd283f'. Called from VDS 'host_mixed_2'
2020-07-02 09:18:50,537+03 WARN  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-17496) [14c64a7d] EVENT_ID: USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM vm_TestCase5138_0209130682 on Host host_mixed_2.

VDSM.log:
2020-07-02 09:18:48,754+0300 ERROR (vm/ad70f664) [virt.vm] (vmId='ad70f664-cf00-4390-a8dc-ccb267dd283f') The vm start 
process failed (vm:871)
Traceback (most recent call last):
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 801, in _startUnderlyingVm
    self._run()
  File "/usr/lib/python3.6/site-packages/vdsm/virt/vm.py", line 2570, in _run
    fname, srcDomXML, libvirt.VIR_DOMAIN_SAVE_PAUSED)
  File "/usr/lib/python3.6/site-packages/vdsm/common/libvirtconnection.py", line 131, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python3.6/site-packages/vdsm/common/function.py", line 94, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 4851, in restoreFlags
    if ret == -1: raise libvirtError ('virDomainRestoreFlags() failed', conn=self)
libvirt.libvirtError: internal error: child reported (status=125): unable to set security context 'system_u:object_r:v
irt_content_t:s0' on '/rhev/data-center/mnt/blockSD/97370c99-3549-4686-8536-d067f82e5daf/images/1bc19190-6f96-4d7e-9db
3-a25c87451aaa/f5dd8cc0-7491-4574-a066-00ffcc0382fb': No such file or directory

Saw it in our automation. After it fails, it starts on another host.
In single host environment, the VM fails to start in the first attempt.


Version-Release number of selected component (if applicable):
rhv-4.4.1-5:
vdsm-4.40.20-1.el8ev.ppc64le
ovirt-engine-4.4.1.5-0.17.el8ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create VM with iSCSI disk
2. Run the VM
3. Create memory snapshot
4. Power off the VM
5. Preview snapshot
6. Run the VM

Actual results:
Operation fails

Expected results:
Operation should succeed.

Additional info:
Logs are attached.
Comment 1 Evelina Shames 2020-07-02 07:23:27 UTC 

*** This bug has been marked as a duplicate of bug 1853194 ***