[Bug 1545302] Please test proposed package
Brian Murray
brian at ubuntu.com
Thu Feb 25 17:49:58 UTC 2016
Hello Paul, or anyone else affected,
Accepted ifupdown into wily-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ifupdown/0.7.54ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: ifupdown (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown #1337873
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Trusty:
Fix Committed
Status in ifupdown source package in Wily:
Fix Committed
Bug description:
[Impact]
* In some configurations recurrent ifup/down calls are broken due to
a false-positive recursion detection.
* In certain situations it leaves interfaces unconfigured (in this
case: WLAN interface connected to WiFi network, but dhcp fails).
[Test Case]
* Setup wpa-roam configuration based on what is in comment #6
* Wait until wpa_supplicant connects to a wifi network
* Run ifconfig to check if the WLAN interface received dhcp info
* Expected result: WLAN is fully configured according to dhcp settings
* Actual result: WLAN is connected to WiFi but not configured
[Regression Potential]
* Fixed upstream, fix present in Xenial.
* Debdiffs contain a backport of an upstream fix.
[Other Info]
* Original bug description:
The following versions of ifupdown introduced a recursion check using "IFUPDOWN_<interface>" environment variables along with a new locking mechanism for ifup (see #1337873):
0.7.47.2ubuntu4.2 (in Trusty)
0.7.54ubuntu1.1 (in Wily)
0.7.54ubuntu2 (in Xenial)
This recursion check breaks the wpa-roam feature of wpasupplicant,
preventing it from loading the logical interface specified by id_str
after associating with an AP. Specifically, after upgrading to one of
the above ifupdown versions, the '/sbin/ifup -v --force
"$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in
functions.sh fails with an "ifup: recursion detected for parent
interface wlan0 in post-up phase" error.
To fix the issue, functions.sh needs to run `unset
"IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from
detecting the recursion. The attached patch implements this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1545302/+subscriptions
More information about the foundations-bugs
mailing list