Bug #38946
ceph_volume_client: Too many arguments for "WriteOpCtx"
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Source:
Development
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
VolumeClient
Labels (FS):
Manila
Pull request ID:
Crash signature:
Description
Sebastian W hit this while linting,
pybind/ceph_volume_client.py:1480: error: Too many arguments for "WriteOpCtx"
https://gist.github.com/sebastian-philipp/25f70aae3b0d21b1a781c110a7ef8be4#file-mypy_report-txt-L22
Related issues
History
#1 Updated by Ramana Raja over 1 year ago
- Status changed from New to Fix Under Review
#2 Updated by Kefu Chai over 1 year ago
- Backport set to mimic,nau
#3 Updated by Kefu Chai over 1 year ago
- Backport changed from mimic,nau to luminous,mimic,nautilus
- Pull request ID set to 27213
#4 Updated by Patrick Donnelly over 1 year ago
- Assignee set to Ramana Raja
- Priority changed from Normal to Urgent
- Target version set to v15.0.0
- Start date deleted (
03/27/2019) - Source set to Development
#5 Updated by Patrick Donnelly over 1 year ago
- Related to Bug #24173: ceph_volume_client: allow atomic update of RADOS objects added
#6 Updated by Ramana Raja over 1 year ago
- Description updated (diff)
- Category set to Correctness/Safety
- Priority changed from Urgent to Normal
#7 Updated by Ramana Raja over 1 year ago
I'm not sure it's worth the trouble to backport to luminous, and mimic. Maybe OK to backport to latest stable release, nautilus?
#8 Updated by Patrick Donnelly over 1 year ago
- Backport changed from luminous,mimic,nautilus to nautilus
#9 Updated by Kefu Chai over 1 year ago
- Status changed from Fix Under Review to Pending Backport
#10 Updated by Nathan Cutler over 1 year ago
- Copied to Backport #39050: nautilus: ceph_volume_client: Too many arguments for "WriteOpCtx" added
#11 Updated by Nathan Cutler about 1 year ago
- Status changed from Pending Backport to Resolved