Project

General

Profile

Actions
Copy link

Bug #40369

closed

ceph_volume_client: fs_name must be converted to string before using it

Added by Rishabh Dave almost 5 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Rishabh Dave
Category:
-
Target version:
Ceph - v15.0.0
% Done:

0%

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

Description

fs_name would normally be assigned a string while creating a CephVolumeClient instance. We need to make sure that it is converted to bytes object to avoid a bug like 39750.

Related issues 2 (0 open — 2 closed)

Copied to CephFS - Backport #40896: mimic: ceph_volume_client: fs_name must be converted to string before using itRejectedNathan CutlerActions
Copied to CephFS - Backport #40897: nautilus: ceph_volume_client: fs_name must be converted to string before using itResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Rishabh Dave almost 5 years ago

  • Assignee set to Rishabh Dave
Actions
Copy link
 #2

Updated by Rishabh Dave almost 5 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 28557
Actions
Copy link
 #3

Updated by Patrick Donnelly almost 5 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v15.0.0
  • Source set to Development
  • Backport set to nautilus,mimic
Actions
Copy link
 #4

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40896: mimic: ceph_volume_client: fs_name must be converted to string before using it added
Actions
Copy link
 #5

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40897: nautilus: ceph_volume_client: fs_name must be converted to string before using it added
Actions
Copy link
 #6

Updated by Nathan Cutler over 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
Copy link
 #7

Updated by Nathan Cutler over 4 years ago

The mimic backport caused a regression, #42317, which was caught during v13.2.7 release preparation, and was reverted by https://github.com/ceph/ceph/pull/31017

My understanding is this should not have been backported to mimic in the first place.

Actions
Copy link

Also available in: Atom PDF