EOF error during SSH connection

Bug #1277439 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

Bug Description

This has been observed during a tempest run: http://paste.openstack.org/show/63009/

It might be a paramiko issue, and might not happen anymore, but it sound like another intermittent failure that need to be tracked with an elastic recheck query.

Full logs: http://logs.openstack.org/90/67390/6/check/check-tempest-dsvm-neutron-isolated/552fb81

Revision history for this message
Darragh O'Reilly (darragh-oreilly) wrote :

I don't see the ssh problem in the logs - I think the ssh connection via the floatingip was ok and "[chan 1] EOF received (1)" is normal?

Is this not the problem http://logs.openstack.org/90/67390/6/check/check-tempest-dsvm-neutron-isolated/552fb81/console.html.gz#_2014-02-07_01_58_54_816

  Traceback (most recent call last):
   File "tempest/scenario/test_cross_tenant_connectivity.py", line 481, in test_cross_tenant_traffic
     self._verify_mac_addr(self.tenants[tenant_id])
   File "tempest/scenario/test_cross_tenant_connectivity.py", line 470, in _verify_mac_addr
     server_ip = self._get_server_ip(tenant.access_point)
   File "tempest/scenario/test_cross_tenant_connectivity.py", line 327, in _get_server_ip
     return server.networks[network_name][0]
   KeyError: u'network-smoke--1752694621'

It seems the "addresses" attribute was empty on the last GET. http://logs.openstack.org/90/67390/6/check/check-tempest-dsvm-neutron-isolated/552fb81/console.html.gz#_2014-02-07_01_58_54_692

RESP BODY: {"server": {"status": "ACTIVE", "updated": "2014-02-07T01:47:45Z", "hostId": "6a46aadcb9b335473c51951cf61a4a8215d59e4ea00e5b632d6276fc", "addresses": {} ...

I checked other logs for a run without this failure and "addresses" had a dict that included the fixed ip and mac.

Revision history for this message
Darragh O'Reilly (darragh-oreilly) wrote :

It has only happened 4 times in the last 7 days:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOiBcInNlcnZlci5uZXR3b3Jrc1tuZXR3b3JrX25hbWVdXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6IjYwNDgwMCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjEzOTIwNDM2ODUyNTN9

There is a useful comment here:
https://github.com/openstack/tempest/blob/103aa1cab91456887bdb457e18c4b4270434ed10/tempest/scenario/manager.py#L472
# The instance retrieved on creation is missing network
# details, necessitating retrieval after it becomes active to
# ensure correct details.

It seems that sometimes does not work.

Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :
Revision history for this message
Eugene Nikanorov (enikanorov) wrote :

Is this bug still valid?

Changed in neutron:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
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.