Bug #23068: TestLibRBD.RenameViaLockOwner may still fail with -ENOENT - rbd - Ceph

Actions

Copy link

Bug #23068

closed

TestLibRBD.RenameViaLockOwner may still fail with -ENOENT

Added by Mykola Golub about 6 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Mykola Golub

Target version:

% Done:

Source:

Tags:

Backport:

luminous,jewel

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

http://qa-proxy.ceph.com/teuthology/trociny-2018-02-20_16:16:39-rbd-wip-mgolub-testing-distro-basic-smithi/2207758/teuthology.log

2018-02-20T16:44:47.460 INFO:tasks.workunit.client.0.smithi001.stdout:/build/ceph-13.0.1-2052-g2511947/src/test/librbd/test_librbd.cc:4586: Failure
2018-02-20T16:44:47.461 INFO:tasks.workunit.client.0.smithi001.stdout:      Expected: 0
2018-02-20T16:44:47.461 INFO:tasks.workunit.client.0.smithi001.stdout:To be equal to: rbd.rename(ioctx, name.c_str(), new_name.c_str())
2018-02-20T16:44:47.461 INFO:tasks.workunit.client.0.smithi001.stdout:      Which is: -2
2018-02-20T16:44:47.466 INFO:tasks.workunit.client.0.smithi001.stdout:[  FAILED  ] TestLibRBD.RenameViaLockOwner (2510 ms)

It was believed to be fixed in #18435, and that fix properly filters out the error coming from the possible race, but the request still completes with non-filtered error code.

Related issues 2 (0 open — 2 closed)