Project

General

Profile

Actions

Bug #41800

closed

qa: logrotate should tolerate connection resets

Added by Patrick Donnelly over 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Q/A
Tags:
Backport:
nautilus,mimic
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
kcephfs
Component(FS):
qa-suite
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

During kclient runs, we reboot nodes. The logrotate exception causes the test to fail:

2019-09-11T18:59:36.253 ERROR:teuthology:Uncaught exception (Hub)
Traceback (most recent call last):
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/virtualenv/local/lib/python2.7/site-packages/gevent/greenlet.py", line 536, in run
    result = self._run(*self.args, **self.kwargs)
  File "/home/teuthworker/src/github.com_ceph_ceph_master/qa/tasks/ceph.py", line 161, in invoke_logrotate
    wait=False,
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/orchestra/cluster.py", line 64, in run
    return [remote.run(**kwargs) for remote in remotes]
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/orchestra/remote.py", line 205, in run
    r = self._runner(client=self.ssh, name=self.shortname, **kwargs)
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/orchestra/run.py", line 432, in run
    r.execute()
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/teuthology/orchestra/run.py", line 102, in execute
    self.client.exec_command(self.command)
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/virtualenv/local/lib/python2.7/site-packages/paramiko/client.py", line 493, in exec_command
    chan = self._transport.open_session(timeout=timeout)
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/virtualenv/local/lib/python2.7/site-packages/paramiko/transport.py", line 806, in open_session
    timeout=timeout,
  File "/home/teuthworker/src/git.ceph.com_git_teuthology_master/virtualenv/local/lib/python2.7/site-packages/paramiko/transport.py", line 933, in open_channel
    raise e
error: [Errno 104] Connection reset by peer

From: /ceph/teuthology-archive/pdonnell-2019-09-10_13:23:49-kcephfs-master-distro-basic-smithi/4295626/teuthology.log

Should be easy to reproduce with: --suite kcephfs --filter client-recovery


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #42278: mimic: qa: logrotate should tolerate connection resetsRejectedActions
Copied to CephFS - Backport #42279: nautilus: qa: logrotate should tolerate connection resetsResolvedNathan CutlerActions
Actions #1

Updated by Venky Shankar over 4 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Venky Shankar over 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 30809
Actions #3

Updated by Patrick Donnelly over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #4

Updated by Nathan Cutler over 4 years ago

  • Backport changed from nautilus,mimimc to nautilus,mimic
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #42278: mimic: qa: logrotate should tolerate connection resets added
Actions #6

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #42279: nautilus: qa: logrotate should tolerate connection resets added
Actions #7

Updated by Nathan Cutler almost 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF