Bug #49860: cephadm adopt - Report conf file missing - now it says could not detect legacy fsid - Orchestrator - Ceph

Actions

Copy link

Bug #49860

closed

cephadm adopt - Report conf file missing - now it says could not detect legacy fsid

Added by Vasishta Shastry about 3 years ago. Updated over 2 years ago.

Status:

Can't reproduce

Priority:

Normal

Assignee:

Category:

cephadm (binary)

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

Ceph - v16.1.0

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

version - cephadm-16.1.0-603.el8cp.noarch

cmd:

  - cephadm
  - --image
  - registry.redhat.io/openshift4/ose-prometheus-alertmanager:v4.6
  - adopt
  - --cluster
  - ceph
  - --name
  - alertmanager.ceph-vasishta-1615821696698-node10-grafana
  - --style
  - legacy
  - --skip-pull

Output -

stderr: 'ERROR: could not detect legacy fsid; set fsid in ceph.conf'

Actually conf file was not existing on the node

So It would be apt if we can Error out to user saying conf file doesn't exist

Actions

Copy link

Updated by Sebastian Wagner almost 3 years ago

Description updated (diff)

Actions

Copy link

Updated by Sebastian Wagner almost 3 years ago

Do you remember, were there any other ceph daemons deployed on that host? cephadm needs to know the fsid of the cluster. if there are no OSD daemons on that host or if there is no /etc/ceph/ceph.conf on that host, if won't be able to know that

Actions

Copy link