Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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)?