Bug 1258765
| Summary: | virt-who rebase | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Radek Novacek <rnovacek> |
| Component: | virt-who | Assignee: | Radek Novacek <rnovacek> |
| Status: | CLOSED ERRATA | QA Contact: | gaoshang <sgao> |
| Severity: | medium | Docs Contact: | Jana Heves <jsvarova> |
| Priority: | high | ||
| Version: | 6.8 | CC: | hsun, jsvarova, ovasik, rbalakri, salmy |
| Target Milestone: | rc | Keywords: | Rebase |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | virt-who-0.16-1.el6 | Doc Type: | Rebase: Bug Fixes and Enhancements |
| Doc Text: |
virt-who rebased to version 0.16-7
* *virt-who* queries of the Hyper-V hypervisor have been extended to include the capacity (socket counts so that the subscription applied to the hypervisor can be evaluated), name, and type to be displayed in the SMS inventory to make it easier for the user to identify the system.
* the *virt-who* interval, "VIRTWHO_INTERVAL=", has been extended to 1 minute to prevent from failures in communication with Subscription-Manager.
* *virt-who* now supports connecting Red Hat Enterprise Virtualization Manager (RHEV-M) and the Hyper-V hypervisor through proxy.
* *virt-who* now allows filtering for hosts that are sent by *virt-who* to Red Hat Subscription-Manager.
* *virt-who* is able to report which virtual guests of virtual machines are active on all known hypervisors.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-05-10 23:56:03 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: | 1167283, 1259038, 1259295, 1272873 | ||
|
Description
Radek Novacek
2015-09-01 08:51:34 UTC
virt-who package is now rebased to virt-who-0.16-1.el6. 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://rhn.redhat.com/errata/RHEA-2016-0859.html |