** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New
** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Fix Released ** Also affects: cloud-init (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Zesty) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1690430 Title: [Hyper-V] Advanced networking support on Azure Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Bug description: We are in the process of rolling out SR-IOV in Azure (available as a preview now, contact me offline and we can work out getting your subscription addedif you want to try it). In general our normal synthetic interface appears as eth0 and the VF comes in as eth1. We intend to bond these interfaces together so that if the VF goes down, or the VM is migrated to where no VF is present, eth0 remains as the valid default interface. At the moment we are handling the bonding via this script: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/plain/tools/hv/bondvf.sh We were looking at ways to either integrate the behavior into cloud- init or invoke the script from cloud-init and do the right thing. We recently observed after https://bugs.launchpad.net/ubuntu/+source /cloud-init/+bug/1669860 that the VF interface gets renamed to something like "enP1p0s2" but more recently as "rename2". Is it possible that 1669860 needs to be expanded to cover our case or is there something we should be doing to make sure that change is working properly for SR-IOV in Azure? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1690430/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp