Bug 1022794

Summary: disorderly awakening of network system
Product: [Fedora] Fedora Reporter: pavel.nedr
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dcbw, pavel.nedr
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:47:50 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:
Attachments:
Description Flags
journalctl log none

Description pavel.nedr 2013-10-24 04:53:03 UTC
Created attachment 815610 [details]
journalctl log

Description of problem:
I found this when I investigate the error of VPN reconnection after S3 sleep mode.

When Fedora woke up, at first the openvpn tryes to restart connection. Then the kernel reports that the network's card link is activated. After that NetworkManager set Carrier to OFF, then to ON (openvpn continues to try to connect to VPN server, in the end it results in an error). After that avahi-daemon reset and initialize IP session and set IP address. After that starting NM's dispatcherd. But it can't connect to my VPN server, because event trigger is set to "$state" = "up".

journalctl log in attach


Version-Release number of selected component (if applicable):
Name        : NetworkManager
Arch        : x86_64
Epoch       : 1
Version     : 0.9.8.2
Release     : 1.fc18
Size        : 3.9 M
Repo        : installed
From repo   : updates

Name        : openvpn
Arch        : x86_64
Version     : 2.3.2
Release     : 4.fc18
Size        : 935 k
Repo        : installed
From repo   : updates

Name        : NetworkManager-openvpn
Arch        : x86_64
Epoch       : 1
Version     : 0.9.3.997
Release     : 3.fc18
Size        : 684 k
Repo        : installed
From repo   : fedora

Comment 1 pavel.nedr 2013-10-24 05:00:55 UTC
computer goes to sleep through pm-suspend

Comment 2 Fedora End Of Life 2015-01-09 20:21:09 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 17:47:50 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.