Project

General

Profile

Actions

Bug #49121

closed

vstart: volumes/nfs interface complaints cluster does not exists

Added by Varsha Rao about 3 years ago. Updated about 3 years ago.

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

0%

Source:
Development
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/nfs
Labels (FS):
NFS-cluster
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

/home/varsha/ceph/build/bin/ceph -c /home/varsha/ceph/build/ceph.conf test_orchestrator load_data -i /home/varsha/ceph/src/pybind/mgr/test_orchestrator/dummy_data.json 
ceph_adm nfs cluster create cephfs vstart 
/home/varsha/ceph/build/bin/ceph -c /home/varsha/ceph/build/ceph.conf nfs cluster create cephfs vstart 
NFS Cluster Created Successfully
ceph_adm nfs export create cephfs a vstart /cephfs 
/home/varsha/ceph/build/bin/ceph -c /home/varsha/ceph/build/ceph.conf nfs export create cephfs a vstart /cephfs 
Error ENOENT: Cluster does not exists

Change cluster name from 'ganesha-vstart' to 'vstart'. Test orchestrator dummy data needs to be updated.

# ./bin/ceph nfs cluster ls
ganesha-vstart


Related issues 2 (0 open2 closed)

Related to CephFS - Bug #49122: vstart: Rados url errorResolvedVarsha Rao

Actions
Copied to CephFS - Backport #49346: pacific: vstart: volumes/nfs interface complaints cluster does not existsResolvedsinguliere _Actions
Actions #1

Updated by Varsha Rao about 3 years ago

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

Updated by Patrick Donnelly about 3 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions #3

Updated by Backport Bot about 3 years ago

  • Copied to Backport #49346: pacific: vstart: volumes/nfs interface complaints cluster does not exists added
Actions #4

Updated by singuliere _ about 3 years ago

  • Related to Bug #49122: vstart: Rados url error added
Actions #5

Updated by Loïc Dachary about 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

Also available in: Atom PDF