Bug #47512
mgr/nfs: Cluster creation throws 'NoneType' object has no attribute 'replace' error in rook
% Done:
0%
Source:
Development
Tags:
Backport:
octopus
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
debug 2020-09-17T08:44:51.429+0000 7fa13b40c700 0 [volumes ERROR volumes.fs.nfs] NFS Cluster test could not be created Traceback (most recent call last): File "/usr/share/ceph/mgr/volumes/fs/nfs.py", line 701, in create_nfs_cluster if cluster_id not in available_clusters(self.mgr): File "/usr/share/ceph/mgr/volumes/fs/nfs.py", line 32, in available_clusters return [cluster.spec.service_id.replace('ganesha-', '', 1) for cluster in completion.result] File "/usr/share/ceph/mgr/volumes/fs/nfs.py", line 32, in <listcomp> return [cluster.spec.service_id.replace('ganesha-', '', 1) for cluster in completion.result] AttributeError: 'NoneType' object has no attribute 'replace'
Related issues
History
#1 Updated by Varsha Rao over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 37214
#2 Updated by Patrick Donnelly over 3 years ago
- Status changed from Fix Under Review to Pending Backport
#3 Updated by Nathan Cutler over 3 years ago
- Copied to Backport #47601: octopus: mgr/nfs: Cluster creation throws 'NoneType' object has no attribute 'replace' error in rook added
#4 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".