Bug #57954: rook/k8s: nfs cluster creation ends up with no daemons deployment - Orchestrator - Ceph

Actions

Copy link

Bug #57954

closed

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

Added by Ben Gao over 1 year ago. Updated about 1 year ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Ceph - v17.2.6

% Done:

Source:

Community (user)

Tags:

backport_processed

Backport:

quincy

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

Ceph - v17.2.5

ceph-qa-suite:

Pull request ID:

48694

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 1 (0 open — 1 closed)