Project

General

Profile

Bug #57954

rook/k8s: nfs cluster creation ends up with no daemons deployment

Added by Ben Gao 3 months ago. Updated 3 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
-
Category:
-
Target version:
% Done:

0%

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

Description

steps to reproduce:
1, with rook deploy Ceph 17.2.5 on k8s
2, run the following to enable rook as orchestrator with the newly deployed ceph:
ceph mgr module enable rook
ceph orch set backend rook
Note: rook currently doesn't work well in the case, need proceed through workaround.
3, create nfs cluster with command line:
Ceph nfs cluster create mynfs
The execution results show cluster created successfully. Actually it didn't. There were no k8s resource(nfs-Ganesha pod) created.

expected result:
ceph command can create nfs cluster successfully as needed.


Related issues

Copied to Orchestrator - Backport #58004: quincy: rook/k8s: nfs cluster creation ends up with no daemons deployment In Progress

History

#1 Updated by Ben Gao 3 months ago

I am working on this issue

#2 Updated by Ben Gao 3 months ago

#3 Updated by Juan Miguel Olmo Martínez 3 months ago

  • Project changed from Ceph to Orchestrator
  • Category deleted (ceph cli)
  • Pull request ID set to 48694

#4 Updated by Juan Miguel Olmo Martínez 3 months ago

  • Status changed from New to Pending Backport
  • Backport set to quincy

#5 Updated by Backport Bot 3 months ago

  • Copied to Backport #58004: quincy: rook/k8s: nfs cluster creation ends up with no daemons deployment added

#6 Updated by Backport Bot 3 months ago

  • Tags set to backport_processed

Also available in: Atom PDF