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

Bug 1283740

Summary:	Access denied on virt-who check in
Product:	[Retired] Katello	Reporter:	Filip Nguyen <fnguyen>
Component:	Webservice API	Assignee:	Katello Bug Bin <katello-bugs>
Status:	CLOSED EOL	QA Contact:	Katello QA List <katello-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	bcourt, csnyder, egolov, hsun, rjerrido, tomckay, wpoteat
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-27 20:06:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Tom McKay 2015-11-19 17:27:30 UTC

Please retry after registering the system that virt-who is running on to the environment desired. My suspicion is that the system is registered to Library. Running virt-who with the system registration credentials gives access only to the same org and lifecycle environment as that system.

Comment 2 Rich Jerrido 2015-11-19 20:30:05 UTC

In the configuration being used, virt-who is installed on the satellite itself (which is not self-registered) and uses the following config:

cat /etc/virt-who.d/vsphere.conf 
[esx-farm]
type=esx
server=vmware.acloud.com
username=administrator
password=<redacted>
owner=Auroracloud
env=Library
hypervisor_id=hostname
rhsm_hostname=satellite.auroracloud.com
rhsm_username=admin
rhsm_encrypted_password=<redacted>
rhsm_prefix=/rhsm


with env=Library, no issues. With env != Library (or omitted) virt-who reporting fails. 


As lifecycle environments don't have much of a place with regards to hypervisors, I would expect that one of the following would be true:

* ENV isn't required
* ENV is silently ignored
* ENV is set on a hypervisor, but serves no purpose other than allowing the user to 'tag' a system. 

As it is currently, If I set ENV to any valid lifecycle environment other than Library, it fails. (and I don't get host/guest maps)

Comment 7 Eko 2019-10-24 05:19:16 UTC

This issue was fixed, env option was removed from virt-who-0.24.6.