Hide Forgot
Description of problem: When viewing the rhsm.log after setting up virt-who, it would be helpful to see where the host-to-guest mapping is reporting to. Even if it just took the output from the owner= in the virt-who config file. Which could be either /etc/virt-who.d/config or /etc/sysconfig/virt-who This is what we see now.. 2016-10-26 15:02:26,930 [INFO] @subscriptionmanager.py:165 - Sending update in hosts-to-guests mapping: If that could show something like this.. 2016-10-26 15:02:26,930 [INFO] @subscriptionmanager.py:165 - Sending update in hosts-to-guests mapping to Default_Organization: then we could see without the config file where the config is pointed to. The /etc/virt-who.d/config - Does not come in a sosreport currently. This would also help us if multiple vcenters are involved ( which is very common). Can help to verify quickly that the owner= is incorrect in the config without having to ask for it. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. install and configure virt-who 2. view the rhsm.log for information/troubleshooting why hosts are not showing up in the portal/satellite6 depending on environment Actual results: does not give us enough information to see where the hosts should be showing up ie portal or satellite Sending update in hosts-to-guests mapping Expected results: Sending update in hosts-to-guests mapping to Default_Organization <--- Additional info:
@Kathryn Just as FYI: /etc/virt-who.d/config is included in recent sosreport for RHEL7 [0] and concerned errata [1] [0] https://bugzilla.redhat.com/show_bug.cgi?id=1353552 [1] https://rhn.redhat.com/errata/RHBA-2016-2380.html
(In reply to Kenny Tordeurs from comment #4) > @Kathryn > > Just as FYI: > > /etc/virt-who.d/config is included in recent sosreport for RHEL7 [0] and > concerned errata [1] > > [0] https://bugzilla.redhat.com/show_bug.cgi?id=1353552 > [1] https://rhn.redhat.com/errata/RHBA-2016-2380.html Kenny thanks for the heads up =D
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:0895