Project

General

Profile

Bug #48656

cephadm botched install of ceph-fuse (symbol lookup error)

Added by Stephen Longofono over 3 years ago. Updated almost 3 years ago.

Status:
Can't reproduce
Priority:
Low
Assignee:
-
Category:
cephadm
Target version:
% Done:

0%

Source:
Community (user)
Tags:
cephadm,ceph-fuse
Backport:
Regression:
No
Severity:
1 - critical
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

As of this morning, installing ceph-fuse via cephadm is broken.

Working on a healthy cluster on nodes running Ubuntu 18.04 server, Ceph octopus v15.2.7, the cephadm tool reports:

$> sudo cephadm install ceph-fuse
INFO:root:Installing packages ['ceph-fuse']...

Using ceph-fuse fails immediately with a complaint about an unknown symbol:

$> sudo ceph-fuse --help
ceph-fuse: symbol lookup error: ceph-fuse: undefined symbol: _ZN8ObjecterC1EPN4ceph6common11CephContextEP9MessengerP9MonClientP8Finisher

This looks like a mangled object name, possibly a bug in the ceph-fuse code?

History

#1 Updated by Stephen Longofono over 3 years ago

Demangled symbol:

$> c++filt _ZN8ObjecterC1EPN4ceph6common11CephContextEP9MessengerP9MonClientP8Finisher
Objecter::Objecter(ceph::common::CephContext*, Messenger*, MonClient*, Finisher*)

Versions:

$> sudo ceph --version
ceph version 15.2.7 (88e41c6c49beb18add4fdb6b4326ca466d931db8) octopus (stable)

$> sudo cephadm version
INFO:cephadm:Using recent ceph image docker.io/ceph/ceph:v15
ceph version 15.2.8 (bdf3eebcd22d7d0b3dd4d5501bee5bac354d5b55) octopus (stable)

This seems to be a mismatch with the version of ceph that cephadm has installed on nodes and the version of ceph that cephadm is from. Is there a way to specify a version to use for either/both during the installation or bootstrap process?

#2 Updated by Stephen Longofono over 3 years ago

Workaround: after bootstrapping and expanding the cluster, manually upgrade ceph via apt/apt-get

#3 Updated by Sebastian Wagner about 3 years ago

tbh, this is somewhat out of scope for cephadm. cephadm mainly cares about containers, not so much about keeping packages on the host system up-to-date

#4 Updated by Sebastian Wagner about 3 years ago

  • Priority changed from Normal to Low

#5 Updated by Sebastian Wagner almost 3 years ago

  • Status changed from New to Can't reproduce

Also available in: Atom PDF