Bug 1414103 - rebase NetworkManager package to new upstream version 1.8.x in rhel-7.4
Summary: rebase NetworkManager package to new upstream version 1.8.x in rhel-7.4
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Francesco Giudici
QA Contact: Desktop QE
Ioanna Gkioka
Depends On:
Blocks: 1393481 1449321 1451424
TreeView+ depends on / blocked
Reported: 2017-01-17 18:39 UTC by Thomas Haller
Modified: 2020-09-10 10:08 UTC (History)
11 users (show)

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.
Clone Of:
: 1449321 (view as bug list)
Last Closed: 2017-08-01 09:22:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2299 0 normal SHIPPED_LIVE Moderate: NetworkManager and libnl3 security, bug fix and enhancement update 2017-08-01 12:40:28 UTC

Description Thomas Haller 2017-01-17 18:39:47 UTC
like for rhel-7.3, where we rebase NetworkManager to upstream 1.4.x release, 

rebase NM againt for rhel-7.4 to the current latest upstream (which will be 1.8.x or even later).

Comment 5 errata-xmlrpc 2017-08-01 09:22:07 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.


Note You need to log in before you can comment on or make changes to this bug.