yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1839800] [NEW] instance need to trigger onupdate when nwinfo update

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Yang Ye <ccyangye@xxxxxxxxx>
Date: Mon, 12 Aug 2019 03:21:24 -0000
Reply-to: Bug 1839800 <1839800@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

When nova got an network-changed event from neutron, it will update instance's info_cache.
But DB model instance's onupdate is not trigger, the field update_at will not be updated.

This is weird because in API `get instance` the network fields changed but updated didn't been changed. 
So you cann't get this result in API when you set changed_since in filters.

We might use orm events in sqlalchemy to solve this problem.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
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/1839800

Title:
  instance need to trigger onupdate when nwinfo update

Status in OpenStack Compute (nova):
  New

Bug description:
  When nova got an network-changed event from neutron, it will update instance's info_cache.
  But DB model instance's onupdate is not trigger, the field update_at will not be updated.

  This is weird because in API `get instance` the network fields changed but updated didn't been changed. 
  So you cann't get this result in API when you set changed_since in filters.

  We might use orm events in sqlalchemy to solve this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1839800/+subscriptions