Reviewed: https://review.openstack.org/424639
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=d79e3afc4c566f439e182f7866969b3392b8a37a
Submitter: Jenkins
Branch:master
commit d79e3afc4c566f439e182f7866969b3392b8a37a
Author: Edan David
Date: Thu Sep 1 03:46:17 2016 -0400
Assign mac address to vf netdevice when using macvtap port
This is a workaround to libvirt issue described here:
https://bugzilla.redhat.com/show_bug.cgi?id=1372944. The problem is that
libvirt dosn't update the mac address of the netdevice, instead it uses
netlink to configure the mac address of the VF. For macvtap to work
libvirt should set the mac address on the VF net device and using
netlink. Until this is fixed we should set both of them in nova.
Change-Id: If32828840b552a73400df052fc12a8b5a24f202d
Closes-Bug: #1622292
** Changed in: nova
Status: In Progress => Fix Released
** Bug watch added: Red Hat Bugzilla #1372944
https://bugzilla.redhat.com/show_bug.cgi?id=1372944
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1622292
Title:
vf interface isn't assigned the correct mac address
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Due to a libvirt change in version libvirt-1.2.18.3-1.fc23.x86_64
Bug ticket for libvirt:
https://bugzilla.redhat.com/show_bug.cgi?id=1372944
the vf interface mac address is not synced with the assigned vf mac address.
when creating a guest with macvtap-passthrough the guest will not get DHCP
because the the VF's netdev name is not set.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1622292/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
