Red Hat Bugzilla – Bug 738678
subscription-manager facts --update will override virt.guests made by virt-who
Last modified: 2015-05-14 11:31:27 EDT
Description of problem:
Current facts collected by virt-who doesn't include virt.guests. As such, subscription-manager facts --update will override virt.guests fact in candlepin posted by virt-who.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open debug for virt-who and enable daemon env var
2. service virt-who start
3. subscription-manager facts --update
4. run virt-who again
after step 4, you will virt-who see virt.guests fact have been changed in candlepin. As a result, it will add virt.guests fact and post facts again to candlepin.
sub-man facts --update should override what virt.guests fact virt-who added
virt-who will not update facts to candlepin if it sees no changes in virt.guests fact.
>sub-man facts --update should override what virt.guests fact virt-who added
sorry, should be
sub-man facts --update should NOT override virt.guests fact virt-who added
This should be addressed by the fix for 737935, once virt-who is modified to use the new API.
Leaving it as ASSIGNED until virt-who update is done. I'll verify once this happens and move to MODIFIED.
Since virt-who no longer updates consumer facts, and instead stores them on the consumer; this bug is no longer an issue.
When this bug was submitted, virt-who would send the list of guestId to candlepin, and candlepin would store them in a fact named virt.guests.
This logic has changed as of virt-who commit:
Since virt-who is no longer updating facts, no overwrite happens.
The new logic is as follows:
Once candlepin receives the list of guest IDs from virt-who, it now stores them on the consumer as guestIds in a seperate database table (cp_consumer_guests), and will appear in the consumer's JSON as guestIds.
Following the new design, this bug no longer exist.