Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1558415

Summary: ovirt-dashboard list of VMs in cockpit is not visible for non-root user
Product: Red Hat Enterprise Virtualization Manager Reporter: Pavol Brilla <pbrilla>
Component: cockpit-ovirtAssignee: Marek Libra <mlibra>
Status: CLOSED WONTFIX QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: low    
Version: 4.1.10CC: cshao, dfediuck, huzhao, jiaczhan, michal.skrivanek, mlibra, mtessun, pbrilla, qiyuan, weiwang, yaniwang, ycui, yzhao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-21 12:09:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pavol Brilla 2018-03-20 08:03:12 UTC
Description of problem:
/var/log/vdsm/cockpit-ovirt.log is created from /usr/share/cockpit/ovirt-dashboard/vdsm/vdsm/vdsm run, and it will have root:root ownership and 644 permissions, which will not allow to see list of VMs to non root user in cockpit

Version-Release number of selected component (if applicable):
cockpit-ovirt-dashboard.noarch             0.10.10-0.el7ev 

How reproducible:
100%

Steps to Reproduce:
1. Create user with kvm group
2. Try to connect to cockpit to check running VMs
3. Several errors on tab, no vms visible

Actual results:
User cannot see vms in cockpit even if (s)he is member of kvm group

Expected results:
See list of VMs
/var/log/vdsm/cockpit-ovirt.log should be owned by vdsm:kvm

Additional info:

Comment 1 Michal Skrivanek 2018-03-21 06:30:59 UTC
Why is it filed downstream?

Marek, does the VM tab still exist in current version? It was supposed to be removed

Comment 2 Pavol Brilla 2018-03-21 12:05:43 UTC
In 4.2 it is completely redesigned. 

This bug was created after conversation in mailing list, and it is against 4.1.10

Comment 5 Franta Kust 2019-05-16 13:08:17 UTC
BZ<2>Jira Resync