Bug 1382640
Summary: | Rebase libvirt to current upstream release | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jiri Denemark <jdenemar> | |
Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> | |
Status: | CLOSED ERRATA | QA Contact: | Xuesong Zhang <xuzhang> | |
Severity: | unspecified | Docs Contact: | Jiri Herrmann <jherrman> | |
Priority: | high | |||
Version: | 7.3 | CC: | dyuan, jdenemar, lersek, mtessun, rbalakri, xuzhang | |
Target Milestone: | rc | Keywords: | Rebase | |
Target Release: | 7.4 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | libvirt-3.2.0-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements | |
Doc Text: |
_libvirt_ rebased to version 3.2.0
The _libvirt_ packages have been upgraded to upstream version 3.2.0, which provides a number of bug fixes and enhancements over the previous version. Notable changes:
* This update makes it possible to install and uninstall specific *libvirt* storage sub-drivers, which reduces the installation footprint.
* You can now configure the `/etc/nsswitch.conf` file to instruct Name Services Switch (NSS) to automatically resolve names of KVM guests to their network addresses.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1382642 1382643 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 17:16:43 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: | 1382642, 1382643, 1395265 |
Description
Jiri Denemark
2016-10-07 09:46:16 UTC
Set the bug to verified since the rebase is done. 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-2017:1846 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-2017:1846 |