Bug 1687126 - Enabling libgfapisupported changes disk image ownership
Summary: Enabling libgfapisupported changes disk image ownership
Keywords:
Status: CLOSED DUPLICATE of bug 1666795
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Gluster
Version: 4.3.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.0
: ---
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-10 06:00 UTC by Hesham
Modified: 2019-05-21 12:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-21 12:08:51 UTC
oVirt Team: Gluster
Embargoed:
pm-rhel: ovirt-4.4+

Attachments (Terms of Use)

Description Hesham 2019-03-10 06:00:37 UTC 
Description of problem:
Enabling LibgfApiSupported setting on oVirt engine causes the disk image file ownership to change to root:root from vdsm:kvm which in turn causes the disks owning VM to fail to start subsequently.  

Version-Release number of selected component (if applicable):
oVirt 4.3.1 

How reproducible:
Every time

Steps to Reproduce:
1. Enable LibgfApiSupported and restart ovirt-engine service 
2. Start any VM and verify it's using libgfapi
3. Shutdown the VM and try to restart it. VM will fail to start
4. Check the ownership of the disk image file, it will be root:root

Changing the ownership of disk images back to vdsm:kvm allows the VM to be started, however the permissions are lost again upon restart. 

Could be related to bug 1666795
Comment 1 Hesham 2019-03-10 06:30:32 UTC 
In some cases the ownership is changed to qemu:qemu however the VM fails to start in those cases too.
Comment 2 Sahina Bose 2019-04-23 06:18:11 UTC 
Could you check if problem persists with oVirt 4.3.2 as the bug 1666795 has been fixed there?
Comment 3 Hesham 2019-05-18 19:20:54 UTC 
I can't reproduce this on 4.3.3
Comment 4 Sahina Bose 2019-05-21 12:08:51 UTC 

*** This bug has been marked as a duplicate of bug 1666795 ***
Note You need to log in before you can comment on or make changes to this bug.