Inconsistent Network info data on port update

[Nachi Ueno]

Description
===========

Neutron support update port to add or modify fixed ip.
Nova support consuming vif_updated_event from Neutron.
However, this event isn't notified for vif driver, so network info data
in nova compute and local network agent state may be inconsistent.

Steps to reproduce
==================

1. Create Port in neutron
2. Create VM in nova
3. Update port

Expected result
===============

vif_driver can consume vif_updated_event

Actual result
=============

There is no way to consume vif updated event.

Environment
===========

We have confirmed this issue environment for OpenContrail driver.

[Matt Riedemann (mriedem)]

What versions of nova and neutron are you using? Mitaka? Newton (master)?

Are you saying neutron is sending a vif updated event or not? If not, then this is a bug in neutron.

[Matt Riedemann (mriedem)]

I'm assuming in your reproduce steps that you boot the server in step 2 with the port from step 1? And then after step 3, you get server details and the update isn't in the addresses dict?

[Nachi Ueno (nati-ueno)]

Sorry for late reply. I was missed your comment.

This is in master.
Neutron is sending port update event and nova-compute consuming it.
However, nova-compute isn't propagating that event for vif_driver.

Yes. Step2 should be launch VM with a port created in Step1.

[Matt Riedemann (mriedem)]

Also, just to be clear, you're using libvirt as the virt driver in nova? Or something else?

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]