Comment 7 for bug 1759056
Revision history for this message
| bugproxy (bugproxy) wrote Comment bridged from LTC Bugzilla | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
------- Comment From <email address hidden> 2018-06-22 08:46 EDT-------
(In reply to comment #13)
> This issue was reported prior to 18.04 GA, using an older version of
> netplan.io. Have you tested the same with a newer version of netplan?
>
> It seems to work just fine here -- with two network interfaces connected to
> the system, I connect using ens6; then modify the netplan configuration to
> move the IP to a newly created bridge (added to the config -- not separately
> created from the command-line), then run 'sudo netplan apply'.
>
> The bridge interface is created and the IP is moved to it, and I do not lose
> connectivity.
>
> On reboot, the system comes up normally, and I have connectivity over br0.
>
> I see no reason for this to behave any differently on tg3, but I've managed
> to get access to a system with such an interface, so I'll test that as well.
the bug was reported for 0.34 version, where it failed to configure bridge and with the latest version of netplan.io 0.36.2, bridge interface is configured. and after reboot the connectivity for br0 comes up.
We can close this bug as fixed