upgrading linux-image package to 4.4.0-103.126 breaks Ceph network file system connection
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ceph (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Xenial |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After clients have upgraded to 4.4.0-103.126 they can no longer connect to the Ceph network.
Using the Grub menu to boot the previous kernel fixes the issue.
The error in dmesg is:
[ 46.811897] FS-Cache: Loaded
[ 46.843670] Key type ceph registered
[ 46.844177] libceph: loaded (mon/osd proto 15/24)
[ 46.863107] FS-Cache: Netfs 'ceph' registered for caching
[ 46.863116] ceph: loaded (mds proto 32)
[ 46.884392] libceph: client3354099 fsid 2efbeab1-
[ 46.886856] libceph: mon0 10.10.2.111:6789 session established
[ 46.897487] ceph: problem parsing mds trace -5
[ 46.897491] ceph: mds parse_reply err -5
[ 46.897492] ceph: mdsc_handle_reply got corrupt reply mds0(tid:1)
All clients are running ceph client version:
ii ceph-fs-common 10.2.9-
Server nodes are running 10.2.6 packages as supplied by Ceph.
All 10.2.* versions are compatible. Using the previous kernel allows the connection to work.
---
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.157.14
RfKill:
Tags: xenial xenial
Uname: Linux 4.4.0-103-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: False
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
tags: | added: kernel-da-key needs-bisect |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in linux (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu Xenial): | |
assignee: | nobody → Joseph Salisbury (jsalisbury) |
Changed in linux (Ubuntu): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
Changed in linux (Ubuntu Xenial): | |
assignee: | Joseph Salisbury (jsalisbury) → nobody |
Changed in linux (Ubuntu): | |
status: | In Progress → Triaged |
Changed in linux (Ubuntu Xenial): | |
status: | In Progress → Triaged |
tags: | removed: kernel-da-key needs-bisect |
Changed in linux (Ubuntu Xenial): | |
status: | Triaged → Fix Committed |
Changed in ceph (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in ceph (Ubuntu Xenial): | |
status: | Confirmed → Invalid |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1737033
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.