Bug 1558415 - ovirt-dashboard list of VMs in cockpit is not visible for non-root user
Summary: ovirt-dashboard list of VMs in cockpit is not visible for non-root user
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: cockpit-ovirt
Version: 4.1.10
Hardware: All
OS: All
low
medium
Target Milestone: ---
: ---
Assignee: Marek Libra
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-20 08:03 UTC by Pavol Brilla
Modified: 2019-05-16 13:08 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-21 12:09:11 UTC
oVirt Team: Virt
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.