You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
I looked into this some with @chambridge but we never did come to a conclusion about exactly why the passwordless sudo user gets different data for virt-what.type than the root user.
I expect them to be the same, and so do our automated tests.
If this is NOT a bug, I need to change the way we test this, but I think that this is not desirable behavior -- since we have the ability to get this data, I think we should get it with a a sudo user.
I think whatever task this is coming from is not using become, it is just trying to run virt-what without using sudo.
Bug Report
Version of rho:
[ 0.30 ]
Expected behavior:
Sudo users should get the same data as the root user.
Actual behavior:
Root user gets: vmware
(passwordless) sudo user gets: N/A (virt-what not found) (even though virt-what is on the machine)
Steps to reproduce:
Scan a virtual machine with virt-what installed (I can provide access to one of our systems) using first the root user, then a seperate scan with a passwordless sudo user.
Environment information:
Type
Operating System
OS Version
Python Version
Virtualization
Scanning System
Fedora
25
3.6
Bare Metal
Target System
RHEL
7,6,5
2.X
ESXi
Target System
Centos
7
2.X
ESXi
Target System
Fedora
26
2.X
ESXi
The text was updated successfully, but these errors were encountered:
Specify type:
Bug severity (if applicable):
Description:
I looked into this some with @chambridge but we never did come to a conclusion about exactly why the passwordless sudo user gets different data for
virt-what.type
than the root user.I expect them to be the same, and so do our automated tests.
If this is NOT a bug, I need to change the way we test this, but I think that this is not desirable behavior -- since we have the ability to get this data, I think we should get it with a a sudo user.
I think whatever task this is coming from is not using become, it is just trying to run
virt-what
without using sudo.Bug Report
Version of rho:
[ 0.30 ]
Expected behavior:
Sudo users should get the same data as the root user.
Actual behavior:
Root user gets:
vmware
(passwordless) sudo user gets:
N/A (virt-what not found)
(even though virt-what is on the machine)Steps to reproduce:
Scan a virtual machine with
virt-what
installed (I can provide access to one of our systems) using first the root user, then a seperate scan with a passwordless sudo user.Environment information:
The text was updated successfully, but these errors were encountered: