Bug 1408556
| Summary: | [RFE] Add where host-to-guests mapping is pointing to in the rhsm.log | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Kathryn Dixon <kdixon> |
| Component: | virt-who | Assignee: | Chris Snyder <csnyder> |
| Status: | CLOSED ERRATA | QA Contact: | Eko <hsun> |
| Severity: | medium | Docs Contact: | Yehuda Zimmerman <yzimmerm> |
| Priority: | high | ||
| Version: | 7.2 | CC: | bcourt, bkearney, csnyder, jherrman, jhnidek, khowell, ktordeur, rjerrido, yuefliu |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: |
*virt-who* logs where the host-guest mapping is sent
The *virt-who* utility now uses the `rhsm.log` file to log the owner or account to which the host-guest mapping is sent. This helps proper configuration of *virt-who*.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-04-10 16:19:53 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: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1420851, 1469152 | ||
|
Description
Kathryn Dixon
2016-12-24 21:47:17 UTC
@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 |