Bug 1365248 - virt-who check-in on registered libvirt hypervisor creates a 2nd consumer
Summary: virt-who check-in on registered libvirt hypervisor creates a 2nd consumer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Candlepin
Classification: Community
Component: candlepin
Version: 0.9.54
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: William Poteat
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-08 17:12 UTC by Justin Sherrill
Modified: 2018-04-06 15:08 UTC (History)
5 users (show)

Fixed In Version: candlepin-2.3.5-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-06 15:08:33 UTC
Embargoed:


Attachments (Terms of Use)
rhsm.log (1.38 KB, text/plain)
2016-08-08 17:13 UTC, Justin Sherrill
no flags Details
candlepin.log (6.37 KB, text/plain)
2016-08-08 17:16 UTC, Justin Sherrill
no flags Details

Description Justin Sherrill 2016-08-08 17:12:04 UTC
Description of problem:

When running virt-who with this configuration:

[libvirt]
type=libvirt
server=qemu:///system
owner=Default_Organization
env=Library
hypervisor_id=hostname
rhsm_prefix=/rhsm

On a libvirt based hypervisor that has registered with subscription-manager, it has been expressed that candlepin should re-use the existing consumer.  What we are seeing is that a second consumer is created.  One for the subscription-manager register, and one for the virt-who checkin.

This makes some types of subscriptions not fully usable such as:
"Red Hat Enterprise Linux, up to 8 guests"


Version-Release number of selected component (if applicable):
candlepin-0.9.54-1.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1.  On a libvirt hypervisor, register with subscription-manager
2.  Install and Configure virt-who as per my config above
3.  Run virt-who -o

Actual results:
Two consumers created

Expected results:
Only one consumer exists, the initial subscription-manager registered consumer is re-used.

Additional info:
Its possible that candlepin is handling this properly but no know one can tell us for sure either way.  As far as we can see it is not.  Regardless of whether candlepin is handling this properly or not, katello will likely need to be enhanced for it to work properly.

Comment 1 Justin Sherrill 2016-08-08 17:13:05 UTC
Created attachment 1188874 [details]
rhsm.log

Comment 2 Justin Sherrill 2016-08-08 17:16:06 UTC
Created attachment 1188878 [details]
candlepin.log


Note You need to log in before you can comment on or make changes to this bug.