Public bug reported: When we added the update_at field to the instance versioned notifications it become visible that nova update the updated_at field of the instance only after the instance is scheduled. However before that step the instance already goes through two state transition and therefore two instance.update notification is emitted with updated_at field being None. This looks contradicting.
Steps to reproduce ================== * (Apply https://review.openstack.org/#/c/475276 if it is not merged yet) * Boot an instance * Observe the update_at field of the instance.update notifications Expected result =============== Every instance.update notification has updated_at field set Actual result ============= The first two instance.update notification is emitted with updated_at field being None Environment =========== * devstack or nova functional test environment with the test case: nova.tests.functional.notification_sample_tests.test_instance.TestInstanceNotificationSample.test_create_delete_server_with_instance_update ** 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/1704928 Title: updated_at field is set on the instance only after it is scheduled Status in OpenStack Compute (nova): New Bug description: When we added the update_at field to the instance versioned notifications it become visible that nova update the updated_at field of the instance only after the instance is scheduled. However before that step the instance already goes through two state transition and therefore two instance.update notification is emitted with updated_at field being None. This looks contradicting. Steps to reproduce ================== * (Apply https://review.openstack.org/#/c/475276 if it is not merged yet) * Boot an instance * Observe the update_at field of the instance.update notifications Expected result =============== Every instance.update notification has updated_at field set Actual result ============= The first two instance.update notification is emitted with updated_at field being None Environment =========== * devstack or nova functional test environment with the test case: nova.tests.functional.notification_sample_tests.test_instance.TestInstanceNotificationSample.test_create_delete_server_with_instance_update To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1704928/+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