Bug 1238865
| Summary: | nm-dispatcher ignores 'pre-down' scripts on suspend | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dominique Brazziel <sixerjman> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | dcbw, lkundrak, orion, psimerda |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.4.0-0.3.git20160621.072358da.fc25 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 19:52:12 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: | |||
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. |
Description of problem: Dispatcher scripts in 'pre-down' ('/etc/NetworkManager/dispatcher.d/pre-down.d') are not executed before suspend. They are executed in the instance of an NM restart. Version-Release number of selected component (if applicable): How reproducible: Select 'Suspend' from the desktop (i.e. XFCE4, GNOME, LXDE, etc.) environment Steps to Reproduce: 1. Select 'Suspend' from the menu in the upper right corner (button has user name) 2. Resume the system 3. Actual results: See the systemd journal entries for 'nm-dispatcher' (journalctl -a _COMM=nm-dispatcher), no script(s) were dispatched for action 'pre-down'. Expected results: Should see messages in the nm-dispatcher journal entries indicating the script(s) in 'pre-down.d' were executed. Additional info: Seems like NM ignores 'pre-down' when it gets the message (via dbus/UPower?) that it should go to sleep. NM begins deactivating the device immediately: (wlan0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37] Jul 02 09:57:17 delldm51 NetworkManager[829]: <info> (wlan0): deactivating device (reason 'sleeping') [37] Jul 02 09:57:17 delldm51 NetworkManager[829]: <info> NetworkManager state is now ASLEEP Jul 02 09:57:36 delldm51 NetworkManager[829]: <info> wake requested (sleeping: yes enabled: yes) Jul 02 09:57:36 delldm51 NetworkManager[829]: <info> waking up... Jul 02 09:57:36 delldm51 NetworkManager[829]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]