Public bug reported: Seen here:
http://logs.openstack.org/90/409890/1/check/gate-nova-tox-db-functional- ubuntu-xenial/17015ce/console.html#_2016-12-12_19_24_33_892626 The differences between the expected notifications on instance.update notifications and what we actually get is the u'ip_addresses': [] is empty in the actual results. There is probably a race where the fake virt driver isn't waiting for the network allocation (which is stubbed out) to complete. ** Affects: nova Importance: Medium Status: Confirmed ** Tags: functional notifications testing ** Changed in: nova Status: New => Confirmed ** Changed in: nova Importance: Undecided => Medium ** Tags added: functional testing ** Tags added: notifications -- 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/1649403 Title: nova.tests.functional.notification_sample_tests.test_instance.TestInstanceNotificationSample.test_create_delete_server_with_instance_update randomly fails with ip_addresses not set in notifications Status in OpenStack Compute (nova): Confirmed Bug description: Seen here: http://logs.openstack.org/90/409890/1/check/gate-nova-tox-db- functional-ubuntu- xenial/17015ce/console.html#_2016-12-12_19_24_33_892626 The differences between the expected notifications on instance.update notifications and what we actually get is the u'ip_addresses': [] is empty in the actual results. There is probably a race where the fake virt driver isn't waiting for the network allocation (which is stubbed out) to complete. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1649403/+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
