[Bug 1759056] Comment bridged from LTC Bugzilla

2018-07-31 Thread bugproxy
--- Comment From nbann...@in.ibm.com 2018-07-23 06:03 EDT--- Configuring Bridge with latest version of netplan is failing again, even after reboot of server. I could see the same error messages that are initially reported in the BUG. I had following entry in netplan yaml and rebooted

[Bug 1759056] Comment bridged from LTC Bugzilla

2018-06-25 Thread bugproxy
--- Comment From abdha...@in.ibm.com 2018-06-25 02:00 EDT--- Perhaps the bridge interface is not pingable after configuration in yaml and run 'netplan apply' command. It requires a machine reboot for the bridge interface to be pingable, I will be opening a separate bug for this. -- You

[Bug 1759056] Comment bridged from LTC Bugzilla

2018-06-22 Thread bugproxy
--- Comment From abdha...@in.ibm.com 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

[Bug 1759056] Comment bridged from LTC Bugzilla

2018-06-12 Thread bugproxy
--- Comment From mputt...@in.ibm.com 2018-06-12 01:49 EDT--- please advice if this issue is being considered in ubuntu 18.04.01? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759056 Title:

[Bug 1759056] Comment bridged from LTC Bugzilla

2018-04-12 Thread bugproxy
--- Comment From abdha...@in.ibm.com 2018-04-12 03:05 EDT--- (In reply to comment #9) > > DEBUG:device enP52p1s0f0 operstate is up, not replugging > > Your ifconfig shows that this interface is up and has a configured IP > address. Do I understand correctly that you encountered this error