Bug 1051401
| Summary: | NetworkManager does not add slaves to new bridge | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Frederic Grelot <fredericg_99> |
| Component: | NetworkManager | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | chkr, dcbw, fredericg_99, iweiss, jklimes, matthew.hirsch, nathanael, nomis80, Simon.Gerhards, steffen, sven, tuksgig |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-15 15:44:26 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
Frederic Grelot
2014-01-10 08:47:38 UTC
Tried also with no success. configured same as above. if i manually bringing up the configured bridge device, i get following error on terminal: $ nmcli connection up bridge-br0 Error: Device 'br0' is waiting for slaves before proceeding with activation. $ brctl show bridge name bridge id STP enabled interfaces br0 0080.000000000000 yes # messages on /var/log/messages during bringing up the bridge interface NetworkManager[4483]: ifcfg-rh: read connection 'bridge-slave-em1' NetworkManager[4483]: <info> (br0): carrier is OFF NetworkManager[4483]: <info> (br0): new Bridge device (driver: 'bridge' ifindex: 11) NetworkManager[4483]: <info> (br0): exported as /org/freedesktop/NetworkManager/Devices/8 NetworkManager[4483]: <info> (br0): No existing connection detected. NetworkManager[4483]: <info> (br0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[4483]: <info> (br0): bringing up device. NetworkManager[4483]: <info> (br0): device state change: unavailable -> disconnected (reason 'none') [20 30 0] NetworkManager[4483]: <info> Activation (br0) starting connection 'bridge-br0' NetworkManager[4483]: <info> (br0): device state change: disconnected -> prepare (reason 'none') [30 40 0] NetworkManager[4483]: <info> Activation (br0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager[4483]: <info> Activation (br0) Stage 1 of 5 (Device Prepare) started... NetworkManager[4483]: <info> Activation (br0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager[4483]: <info> Activation (br0) Stage 1 of 5 (Device Prepare) complete. NetworkManager[4483]: <info> Activation (br0) Stage 2 of 5 (Device Configure) starting... NetworkManager[4483]: <info> (br0): device state change: prepare -> config (reason 'none') [40 50 0] NetworkManager[4483]: <info> Activation (br0) Stage 2 of 5 (Device Configure) successful. NetworkManager[4483]: <info> Activation (br0) Stage 2 of 5 (Device Configure) complete. NetworkManager[4483]: <info> Activation (br0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager[4483]: <info> Activation (br0) Stage 3 of 5 (IP Configure Start) started... NetworkManager[4483]: <info> (br0): device state change: config -> ip-config (reason 'none') [50 70 0] NetworkManager[4483]: <info> (br0): IPv4 config waiting until carrier is on NetworkManager[4483]: <info> (br0): IPv6 config waiting until carrier is on NetworkManager[4483]: <info> Activation (br0) Stage 3 of 5 (IP Configure Start) complete. avahi-daemon[637]: Registering new address record for fe80::ec7c:16ff:fe41:6b2b on br0.*. Same results here with KDE applet. Hi, I found out a working solution. Not the best solution at this time. try these steps: # nmcli con add type bridge ifname br0 # nmcli con add type bridge-slave ifname em1 master br0 # nmcli dev disconnect em1 # nmcli con up bridge-slave-em1 # brctl show >bridge name bridge id STP enabled interfaces >br0 0080.5c260a447c0b yes em1 >virbr0 8000.000000000000 yes founded hints at: https://lists.fedoraproject.org/pipermail/devel/2014-January/194201.html I can confirm Steffen's work around works. This is also a regression from F20 since I could setup a bridge using the normal GUI tools. When I upgraded to F21 the bridge stopped working and I didn't have time to fix it. I had to delete all my original F20 working bridge configuration and follow comment #3 to get it working. I'm willing to help test git versions or whatever patches to see if we can get it fixed and working again. This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22 The thing is that bringing up a bridge (master) in NetworkManager doesn't bring up its slaves. You need to activate slave to bring up the bridge (master is activated automatically as a slave dependency). So the key command here is 'nmcli con up bridge-slave-em1' activating the slave. Note: the nmcli commands can (should) be run as a normal user. However, there is an RFE for introducing an option for bringing up slaves automatically when master was activated - bug 1158529. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Implemented in https://bugzilla.gnome.org/show_bug.cgi?id=735052 and in Fedora now. |