On a second thought it might be not fair to require nova to wait for some events from neutron on cleanup. Also in case of live migration vifs on source node are deleted after vm is already migrated and ports are active on destination node, so neutron will not send any network-vif- unplugged events in this case. Shelve-unshelve seems a corner case and I'd like to avoid hacks in vm cleanup logic.
The other idea for the fix (on neutron side now) would be to change port status to smth like PENDING_BUILD right after db update. Nova will count such ports as non-ACTIVE and will wait for network-vif-plugged events for them. When agent requests info for the port, neutron server will update status to BUILD. Later when agent reports device up, the port will be put back into ACTIVE state and network-vif-plugged event will be sent to nova. Changing project back to neutron. ** Project changed: nova => neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1522824 Title: DVR multinode job: test_shelve_instance failure due to SSHTimeout Status in neutron: New Bug description: gate-tempest-dsvm-neutron-multinode-full fails from time to time due to tempest.scenario.test_shelve_instance.TestShelveInstance.test_shelve_instance failure: Captured traceback: 2015-12-04 01:17:12.569 | ~~~~~~~~~~~~~~~~~~~ 2015-12-04 01:17:12.569 | Traceback (most recent call last): 2015-12-04 01:17:12.570 | File "tempest/test.py", line 127, in wrapper 2015-12-04 01:17:12.570 | return f(self, *func_args, **func_kwargs) 2015-12-04 01:17:12.570 | File "tempest/scenario/test_shelve_instance.py", line 101, in test_shelve_instance 2015-12-04 01:17:12.570 | self._create_server_then_shelve_and_unshelve() 2015-12-04 01:17:12.570 | File "tempest/scenario/test_shelve_instance.py", line 93, in _create_server_then_shelve_and_unshelve 2015-12-04 01:17:12.570 | private_key=keypair['private_key']) 2015-12-04 01:17:12.570 | File "tempest/scenario/manager.py", line 645, in get_timestamp 2015-12-04 01:17:12.571 | private_key=private_key) 2015-12-04 01:17:12.571 | File "tempest/scenario/manager.py", line 383, in get_remote_client 2015-12-04 01:17:12.571 | linux_client.validate_authentication() 2015-12-04 01:17:12.571 | File "tempest/common/utils/linux/remote_client.py", line 63, in validate_authentication 2015-12-04 01:17:12.571 | self.ssh_client.test_connection_auth() 2015-12-04 01:17:12.571 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 167, in test_connection_auth 2015-12-04 01:17:12.571 | connection = self._get_ssh_connection() 2015-12-04 01:17:12.572 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 87, in _get_ssh_connection 2015-12-04 01:17:12.572 | password=self.password) 2015-12-04 01:17:12.572 | tempest_lib.exceptions.SSHTimeout: Connection to the 172.24.5.209 via SSH timed out. 2015-12-04 01:17:12.572 | User: cirros, Password: None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1522824/+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
