Bug 1452648 - (null) in old route syntaxt after calling nmcli modify ipv4.routes
Summary: (null) in old route syntaxt after calling nmcli modify ipv4.routes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-19 12:12 UTC by Vladimir Benes
Modified: 2017-08-01 09:28 UTC (History)
7 users (show)

Fixed In Version: NetworkManager-1.8.0-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:28:57 UTC


Attachments (Terms of Use)
[PATCH] ifcfg-rh: omit empty next hop for routes in legacy format (5.28 KB, patch)
2017-05-19 15:36 UTC, Beniamino Galvani
no flags Details | Diff


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

Description Vladimir Benes 2017-05-19 12:12:27 UTC
Description of problem:
I set route for eth1 device:
echo '192.168.122.3 src 192.168.3.10 dev eth1' > /etc/sysconfig/network-scripts/route-ethie

and callled:
[root@qe-dell-ovs5-vm-43 NetworkManager]# nmcli connection modify ethie ipv4.routes 1.2.3.4

[root@qe-dell-ovs5-vm-43 NetworkManager]# cat /etc/sysconfig/network-scripts/route-ethie
1.2.3.4/32 via (null)

Version-Release number of selected component (if applicable):
1.8.0-2

Comment 1 Beniamino Galvani 2017-05-19 15:36:35 UTC
Created attachment 1280444 [details]
[PATCH] ifcfg-rh: omit empty next hop for routes in legacy format

Comment 2 Thomas Haller 2017-05-19 15:47:54 UTC
(In reply to Beniamino Galvani from comment #1)
> Created attachment 1280444 [details]
> [PATCH] ifcfg-rh: omit empty next hop for routes in legacy format

lgtm

Comment 5 errata-xmlrpc 2017-08-01 09:28:57 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


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