Project

General

Profile

Actions
Copy link

Bug #40095

closed

[CLI]rbd: get positional argument error when using --image

Added by wb song almost 5 years ago. Updated over 4 years ago.

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

0%

Source:
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
28313
Crash signature (v1):
Crash signature (v2):

Description

$ rbd image-meta set --image test1 rbd_cache false
rbd: metadata value was not specified

PR: https://github.com/ceph/ceph/pull/28313

Related issues 3 (0 open — 3 closed)

Copied to rbd - Backport #40233: luminous: [CLI]rbd: get positional argument error when using --imageResolvedJason DillamanActions
Copied to rbd - Backport #40234: mimic: [CLI]rbd: get positional argument error when using --imageResolvedJason DillamanActions
Copied to rbd - Backport #40235: nautilus: [CLI]rbd: get positional argument error when using --imageResolvedPrashant DActions
Actions
Copy link
 #1

Updated by Mykola Golub almost 5 years ago

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

Updated by Mykola Golub almost 5 years ago

  • Backport set to nautilus,mimic,luminous
Actions
Copy link
 #3

Updated by Jason Dillaman almost 5 years ago

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

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40233: luminous: [CLI]rbd: get positional argument error when using --image added
Actions
Copy link
 #5

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40234: mimic: [CLI]rbd: get positional argument error when using --image added
Actions
Copy link
 #6

Updated by Nathan Cutler almost 5 years ago

  • Copied to Backport #40235: nautilus: [CLI]rbd: get positional argument error when using --image added
Actions
Copy link
 #7

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

Also available in: Atom PDF