No responce from metadata server when reusing port

Bug #1868867 reported by Vasyl Saienko
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)

Bug Description

The metadata server returns 404 when using the same port for new instance in
less than cache_timeout.

Steps to reproduce:
1. Enable metadata caching
2. Run test neutron_tempest_plugin.scenario.test_ports.PortsTest.test_previously_used_port
3. The test will fail with

Traceback (most recent call last):

  File "/var/lib/openstack/lib/python3.6/site-packages/tempest/lib/common/", line 107, in _get_ssh_connection


  File "/var/lib/openstack/lib/python3.6/site-packages/paramiko/", line 446, in connect


  File "/var/lib/openstack/lib/python3.6/site-packages/paramiko/", line 764, in _auth

    raise saved_exception

  File "/var/lib/openstack/lib/python3.6/site-packages/paramiko/", line 664, in _auth

    self._transport.auth_publickey(username, pkey)

  File "/var/lib/openstack/lib/python3.6/site-packages/paramiko/", line 1580, in auth_publickey

    return self.auth_handler.wait_for_response(my_event)

  File "/var/lib/openstack/lib/python3.6/site-packages/paramiko/", line 250, in wait_for_response

    raise e

paramiko.ssh_exception.AuthenticationException: Authentication failed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

  File "/var/lib/openstack/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/", line 74, in test_previously_used_port


  File "/var/lib/openstack/lib/python3.6/site-packages/neutron_tempest_plugin/scenario/", line 217, in check_connectivity


  File "/var/lib/openstack/lib/python3.6/site-packages/neutron_tempest_plugin/common/", line 153, in connect

    *args, **kwargs)

  File "/var/lib/openstack/lib/python3.6/site-packages/tempest/lib/common/", line 121, in _get_ssh_connection


tempest.lib.exceptions.SSHTimeout: Connection to the via SSH timed out.

User: cirros, Password: None

tags: added: metadata network
Changed in nova:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Vasyl Saienko (vsaienko) wrote :

I think the issue was fixed on neutron side by:

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.