Project

General

Profile

Bug #47964

ceph-fuse RPM package must same-version ceph rpm

Added by Frédéric Schaer over 3 years ago. Updated over 3 years ago.

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

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
ceph-fuse
Labels (FS):
crash
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Hi,

I just got a hard time debugging why a ceph-fuse client suddendly was not able to mount cephfs.
Not only that, but ceph-fuse was not even displaying a single string even when started in foreground debug mode. nothing.
Ity was just hanging.

There was just a process starting and hanging in the background in addition to ceph-fuse : /usr/bin/python2.7 /usr/bin/ceph-crash

After a closer look, it seems that there was an automated rpm ceph update during the night from 14.2.11 to 14.2.12.
But cephfs was not updated, I don't know why yet.

The result was that only ceph-fs was left as 14.2.11, all other ceph rpms were 14.2.12 on that machine, and that caused a silent ceph-fuse mount failure.
I think there is a missing dependency here, as the RPMs should not have been able to update if breaking ceph-fuse.

Looking at dependencies, nothing requires ceph-fuse :

# rpm -q --whatrequires ceph-fuse
no package requires ceph-fuse

ceph-fuse seems to only require libceph-common.so.0()(64bit)

But it seems to me the breakage I just faced prooves ceph-fuse requires more than just a version of libceph-common, it looks like ceph-fuse 14.2.12 requires ceph 14.2.12. And ceph-fuse 14.2.11 requires ceph 14.2.11.

This bug is related to this other bug : https://tracker.ceph.com/issues/46374

Regards


Related issues

Related to CephFS - Bug #46374: ceph-fuse blocks forever, fails to start, emits no errors New

History

#1 Updated by Patrick Donnelly over 3 years ago

Frédéric Schaer wrote:

Hi,

I just got a hard time debugging why a ceph-fuse client suddendly was not able to mount cephfs.
Not only that, but ceph-fuse was not even displaying a single string even when started in foreground debug mode. nothing.
Ity was just hanging.

There was just a process starting and hanging in the background in addition to ceph-fuse : /usr/bin/python2.7 /usr/bin/ceph-crash

After a closer look, it seems that there was an automated rpm ceph update during the night from 14.2.11 to 14.2.12.
But cephfs was not updated, I don't know why yet.

You need to track down that automated rpm update. It is never safe to automate package upgrades of Ceph without following upgrade procedures.

The result was that only ceph-fs was left as 14.2.11, all other ceph rpms were 14.2.12 on that machine, and that caused a silent ceph-fuse mount failure.
I think there is a missing dependency here, as the RPMs should not have been able to update if breaking ceph-fuse.

It could be a shared library dependency was not met. I don't know why that would lead to a hang and not a crash.

Looking at dependencies, nothing requires ceph-fuse :

[...]

ceph-fuse seems to only require libceph-common.so.0()(64bit)

But it seems to me the breakage I just faced prooves ceph-fuse requires more than just a version of libceph-common, it looks like ceph-fuse 14.2.12 requires ceph 14.2.12. And ceph-fuse 14.2.11 requires ceph 14.2.11.

This bug is related to this other bug : https://tracker.ceph.com/issues/46374

Ya, probably. The mystery remains though.

#2 Updated by Patrick Donnelly over 3 years ago

  • Related to Bug #46374: ceph-fuse blocks forever, fails to start, emits no errors added

Also available in: Atom PDF