Bug 1234478

Summary: no ipv4 loopback ip with NetworkManager-1.0.4-0.1.git20150618.8cffaf3bf5.fc23.x86_64
Product: [Fedora] Fedora Reporter: Kevin Fenzi <kevin>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bruno, dcbw, jklimes, lkundrak, psimerda
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-23 07:51:37 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:

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 ***