Project

General

Profile

Actions

Bug #46123

closed

ceph config show does not display fsid correctly

Added by Nathan Cutler almost 4 years ago. Updated over 3 years ago.

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

0%

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

Description

ubuntu@smithi122:~/ceph/build$ ./bin/ceph config show mon.a fsid
00000000-0000-0000-0000-000000000000

ubuntu@smithi122:~/ceph/build$ ./bin/ceph config show osd.0 fsid
00000000-0000-0000-0000-000000000000

ubuntu@smithi122:~/ceph/build$ ./bin/ceph config show-with-defaults mon.a
fsid 00000000-0000-0000-0000-000000000000
default

From mon.a.log

2019-11-14T19:08:04.589+0000 7fcda2f603c0 0 /home/ubuntu/ceph/build/bin/ceph-mon: set fsid to 71723bec-5eef-4875-8337-1eff03033019


Related issues 3 (0 open3 closed)

Copied from mgr - Bug #42820: ceph config get does not display fsid correctlyResolved

Actions
Copied to mgr - Backport #46183: octopus: ceph config show does not display fsid correctlyResolvedLaura PaduanoActions
Copied to mgr - Backport #46184: nautilus: ceph config show does not display fsid correctlyResolvedNeha OjhaActions
Actions #1

Updated by Nathan Cutler almost 4 years ago

  • Copied from Bug #42820: ceph config get does not display fsid correctly added
Actions #2

Updated by Nathan Cutler almost 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 35662
Actions #3

Updated by Neha Ojha almost 4 years ago

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

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #46183: octopus: ceph config show does not display fsid correctly added
Actions #5

Updated by Nathan Cutler almost 4 years ago

  • Copied to Backport #46184: nautilus: ceph config show does not display fsid correctly added
Actions #6

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

Also available in: Atom PDF