Bug 1234478 - no ipv4 loopback ip with NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5.fc23.x86_64
Summary: no ipv4 loopback ip with NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5.fc23...
Keywords:
Status: CLOSED DUPLICATE of bug 1234121
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-22 15:40 UTC by Kevin Fenzi
Modified: 2015-06-23 07:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-23 07:51:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Kevin Fenzi 2015-06-22 15:40:05 UTC 
After upgrading to NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5.fc23.x86_64 in rawhide I get no 127.0.0.1 ipv4 address on lo. 

This results in dnssec-triggerd and possibly some other things getting mad because they cannot bind to it.
Comment 1 Bruno Wolff III 2015-06-22 15:58:37 UTC 
I am seeing this on one f22 machine, but not another, so it looks like there is some other factor involved in triggering the issue.
Comment 2 Bruno Wolff III 2015-06-23 03:19:42 UTC 
After several consectutive failures on one machine, I downgraded the NetworkManager packages and things worked normally the next boot.
Comment 3 Bruno Wolff III 2015-06-23 03:46:15 UTC 
After upgrading back to 1.0.4-0.1.git20150618.8cffaf3bf5.fc22.i686, the problem returned.
Comment 4 Jirka Klimes 2015-06-23 07:51:37 UTC 
Would you attach output of 'ip addr' when you hit the issue? And also NetworkManager logs, possibly with debug level. Thanks.

$ nmcli g l level debug
or put the following to NetworkManager.conf
[logging]
level=DEBUG

*** This bug has been marked as a duplicate of bug 1234121 ***
Note You need to log in before you can comment on or make changes to this bug.