Bug 1373097

Summary:	virt-who run at remote libvirt mode with wrong env still work normally when report mapping to SAM
Product:	Red Hat Satellite	Reporter:	Liushihui <shihliu>
Component:	Candlepin	Assignee:	Barnaby Court <bcourt>
Status:	CLOSED WONTFIX	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	Unspecified	CC:	bbuckingham, jcallaha
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-22 19:12:07 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:

Description Liushihui 2016-09-05 07:30:38 UTC

Description of problem:
Configure wrong env in /etc/sysconfig/virt-who or /etc/virt-who.d/xxx when virt-who run at remote libvirt mode against SAM, virt-who still work normally.

Version-Release number of selected component (if applicable):
virt-who-0.17-10.el7.noarch
subscription-manager-1.17.11-1.el7.x86_64
python-rhsm-1.17.7-1.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Register system to SAM
2. Configure virt-who run at remote libvirt mode with wrong env in /etc/sysconfig/virt-who or /etc/virt-who.d/xxx
# cat /etc/virt-who.d/virt
[test-libvirt]
type=libvirt
server=qemu+ssh://hp-z220-06.qe.lab.eng.nay.redhat.com/system
username=root
password=qwer1234P!
owner=ACME_Corporation
env=xxxxx ==================> It should be "Library"  
3. Restart virt-who and check virt-who's log


Actual results:
Virt-who can send mapping info to SAM successfully.

Expected results:
It should show error info in log as the following:
"Couldn't find environment 'xxxxx'"

Additional info:
1. It hasn't this problem when run virt-who with CLI mode with wrong env.
2. It also hasn't this problem when virt-who run at hyperv mode/xen mode/esx mode at the same condition.

Comment 1 Radek Novacek 2016-09-06 08:28:41 UTC

There is nothing virt-who can do about this. It doesn't know if environment is correct or not. Incorrect environment must be raised by Candlepin.

If hyperv/xen/esx modes shows an error when env is wrong, remote libvirt should also show an error.

Reassigning to candlepin. Is there any difference in handling remote libvirt and other hypervisors (all of them uses hypervisorCheckIn call)?

Comment 3 Barnaby Court 2016-09-22 19:12:07 UTC

SAM is receiving security updates only