Project

General

Profile

Actions
Copy link

Bug #44433

closed

mgr/dashboard: EC profile, clay plugin is missing

Added by Anonymous about 4 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Stephan Müller
Category:
Component - Pools
Target version:
Ceph - v16.0.0
% Done:

0%

Source:
Tags:
Backport:
octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
37440
Crash signature (v1):
Crash signature (v2):

Description

When creating an erasure code profile, the user can choose between differnt plugins. In this list, the clay plugin is missing, even though one can use it on the cli.

It is also missing in the osd_erasure_code_plugins configuration.

Related issues 1 (0 open — 1 closed)

Copied to Dashboard - Backport #47975: octopus: mgr/dashboard: EC profile, clay plugin is missingResolvedTatjana DehlerActions
Actions
Copy link
 #1

Updated by Lenz Grimmer over 3 years ago

  • Translation missing: en.field_tag_list set to feature-gap, administration
  • Subject changed from mrg/dashboard: EC profile, clay plugin is missing to mgr/dashboard: EC profile, clay plugin is missing
  • Category set to 137
Actions
Copy link
 #2

Updated by Lenz Grimmer over 3 years ago

  • Tracker changed from Feature to Bug
  • Description updated (diff)
  • Regression set to No
  • Severity set to 3 - minor
Actions
Copy link
 #3

Updated by Lenz Grimmer over 3 years ago

  • Assignee set to Stephan Müller
  • Backport set to octopus
Actions
Copy link
 #4

Updated by Stephan Müller over 3 years ago

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

Updated by Lenz Grimmer over 3 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v16.0.0
Actions
Copy link
 #6

Updated by Nathan Cutler over 3 years ago

  • Copied to Backport #47975: octopus: mgr/dashboard: EC profile, clay plugin is missing added
Actions
Copy link
 #7

Updated by Nathan Cutler over 3 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
 #8

Updated by Ernesto Puerta about 3 years ago

  • Project changed from mgr to Dashboard
  • Category changed from 137 to Component - Pools
Actions
Copy link

Also available in: Atom PDF