Project

General

Profile

Actions

Bug #17046

closed

"libvirt: XML-RPC error : Cannot recv data: ssh: connect to host mira044.front.sepia.ceph.com port 22"

Added by Yuri Weinstein over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Category:
Test Node
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rbd
Crash signature (v1):
Crash signature (v2):

Description

Seems like issue with mira044

Run: http://pulpito.ceph.com/yuriw-2016-08-15_16:34:54-rbd-master-distro-basic-vps/
Jobs: many
Logs: http://qa-proxy.ceph.com/teuthology/yuriw-2016-08-15_16:34:54-rbd-master-distro-basic-vps/365553/teuthology.log

2016-08-15T21:45:56.793 INFO:teuthology.task.internal:waiting for more vps machines to be free (need 2 + 3, have 2)...
2016-08-15T21:46:06.824 INFO:teuthology.task.internal:waiting for more vps machines to be free (need 2 + 3, have 3)...
2016-08-15T21:46:16.856 DEBUG:teuthology.lock:lock_many request: {'count': 3, 'locked_by': 'scheduled_yuriw@teuthology', 'description': '/home/teuthworker/archive/yuriw-2016-08-15_16:34:54-rbd-master-distro-basic-vps/365553', 'machine_type': 'vps'}
2016-08-15T21:46:16.896 DEBUG:teuthology.lock:locked ubuntu@vpm157.front.sepia.ceph.com, ubuntu@vpm159.front.sepia.ceph.com, ubuntu@vpm123.front.sepia.ceph.com
2016-08-15T21:46:16.937 INFO:teuthology.provision.downburst:Provisioning a ubuntu 14.04 vps
2016-08-15T21:46:19.522 INFO:teuthology.provision.downburst:Downburst failed on ubuntu@vpm157.front.sepia.ceph.com: libvirt: XML-RPC error : Cannot recv data: ssh: connect to host mira044.front.sepia.ceph.com port 22: No route to host: Connection reset by peer
Traceback (most recent call last):
  File "/home/teuthworker/src/downburst/virtualenv/bin/downburst", line 9, in <module>
    load_entry_point('downburst', 'console_scripts', 'downburst')()
  File "/home/teuthworker/src/downburst/downburst/cli.py", line 64, in main
    return args.func(args)
  File "/home/teuthworker/src/downburst/downburst/create.py", line 22, in create
    conn = libvirt.open(args.connect)
  File "/home/teuthworker/src/downburst/virtualenv/local/lib/python2.7/site-packages/libvirt.py", line 255, in open
    if ret is None:raise libvirtError('virConnectOpen() failed')
libvirt.libvirtError: Cannot recv data: ssh: connect to host mira044.front.sepia.ceph.com port 22: No route to host: Connection reset by peer
2016-08-15T21:46:19.523 ERROR:teuthology.lock:Unable to create virtual machine: ubuntu@vpm157.front.sepia.ceph.com
2016-08-15T21:46:22.523 ERROR:teuthology.provision.downburst:Error destroying vpm157.front.sepia.ceph.com: libvirt: XML-RPC error : Cannot recv data: ssh: connect to host mira044.front.sepia.ceph.com port 22: No route to host: Connection reset by peer
Traceback (most recent call last):
  File "/home/teuthworker/src/downburst/virtualenv/bin/downburst", line 9, in <module>
    load_entry_point('downburst', 'console_scripts', 'downburst')()
  File "/home/teuthworker/src/downburst/downburst/cli.py", line 64, in main
    return args.func(args)
  File "/home/teuthworker/src/downburst/downburst/destroy.py", line 42, in destroy
    conn = libvirt.open(args.connect)
  File "/home/teuthworker/src/downburst/virtualenv/local/lib/python2.7/site-packages/libvirt.py", line 255, in open
    if ret is None:raise libvirtError('virConnectOpen() failed')
libvirt.libvirtError: Cannot recv data: ssh: connect to host mira044.front.sepia.ceph.com port 22: No route to host: Connection reset by peer

2016-08-15T21:46:22.523 ERROR:teuthology.lock:destroy failed for vpm157.front.sepia.ceph.com

Files

Screenshot from 2016-08-16 13-09-33.png (32.2 KB) Screenshot from 2016-08-16 13-09-33.png mira044 console David Galloway, 08/16/2016 05:10 PM
Actions #1

Updated by David Galloway over 7 years ago

  • Category set to Test Node
  • Status changed from New to In Progress
  • Assignee set to David Galloway
  • Priority changed from Urgent to High

Marked VPSes down. Investigating.

Actions #3

Updated by David Galloway over 7 years ago

  • Status changed from In Progress to Resolved

This machine was woefully out of date. Its network settings were still set to static indicating it hasn't been reimaged since Irvine.

I opted to reimage the host and set up its VMs again from scratch.

Actions

Also available in: Atom PDF