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
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
