Bug 1414103
| Summary: | rebase NetworkManager package to new upstream version 1.8.x in rhel-7.4 | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Thomas Haller <thaller> | |
| Component: | NetworkManager | Assignee: | Francesco Giudici <fgiudici> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | medium | Docs Contact: | Ioanna Gkioka <igkioka> | |
| Priority: | medium | |||
| Version: | 7.4 | CC: | aloughla, atragler, bgalvani, fgiudici, fweimer, kabbott, lrintel, rkhan, sukulkar, thaller, vbenes | |
| Target Milestone: | rc | Keywords: | Rebase | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | NetworkManager-1.8.0-0.2.git20170215.1d40c5f4.el7 | Doc Type: | Release Note | |
| Doc Text: |
_NetworkManager_ rebased to version 1.8
The _NetworkManager_ package has been upgraded to upstream version 1.8, which provides a number of bug fixes and enhancements over the previous version. Notable changes include:
* Support for additional route options has been added.
* Managed state of device until reboot has been persisted.
* Devices that are externally managed are now correctly handled.
* Networked reliability on multihomed hosts has been enhanced.
* Hostname management is now more flexibly configured.
* Support for changing and enforcing `802-3 link properties` has been added.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1449321 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 09:22:07 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: | 1393481, 1449321, 1451424 | |||
|
Description
Thomas Haller
2017-01-17 18:39:47 UTC
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/RHSA-2017:2299 |