Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2304313

Summary:	[RFE] Kernel client support for upmap-read
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Santosh Pillai <sapillai>
Component:	RBD	Assignee:	Ilya Dryomov <idryomov>
Status:	CLOSED UPSTREAM	QA Contact:	Sunil Angadi <sangadi>
Severity:	high	Docs Contact:	Rivka Pollack <rpollack>
Priority:	unspecified
Version:	9.0	CC:	bhubbard, ceph-eng-bugs, cephqe-warriors, idryomov, ngangadh, nojha, pdhiran, rpollack, sangadi, vumrao
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	9.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.Kernel client does not support pg-upmap-primary The kernel client currently does not support the `pg-upmap-primary` feature. As a result, users may encounter issues when attempting to mount images or filesystems using the kernel client in environments where `pg-upmap-primary` is configured. If issues occur during mounting with the kernel client, verify that the issue is due to this support issue. 1. Confirm that your cluster contains `pg-upmap-primary` mappings. ---- ceph osd dump \| grep "pg_upmap_primary" ---- 2. Check the kernel log for the following error message. ---- $ dmesg \| tail [73393.901029] libceph: mon2 (1)10.64.24.186:6789 feature set mismatch, my 2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000 [73393.901037] libceph: mon2 (1)10.64.24.186:6789 missing required protocol features ---- These error details confirm that the cluster is using features that the kernel client does not currently support. * If this error message is not emitted, contact Support. * With this error message continue by removing the related mappings. As a workaround, remove the related `pg-upmap-primary` mappings. 1. If using the balancer module, change the mode back to one that does not use `pg-upmap-primary`. This prevents additional mappings from being made. ---- ceph balancer mode upmap ---- 2. Remove all `pg-upmap-primary` mappings. ---- ceph osd rm-pg-upmap-primary-all ----	Story Points:	---
Clone Of:
Clones:	2342210 (view as bug list)		Environment:
Last Closed:	2026-03-04 08:54:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2342210, 2388233

Description Santosh Pillai 2024-08-13 12:56:20 UTC

Description of problem:

QE tried to create a application POD in ODF using cephfs volume. But the process failed with following error in kernel. 

2024-08-13T05:16:58.450979+0000 kernel: libceph: mon2 (2)172.30.233.144:3300 session established
2024-08-13T05:16:58.451124+0000 kernel: libceph: RADOS feature set mismatch: server's required > my supported 0x2f018fb87aa4aafe, missing 0x80000000
2024-08-13T05:16:58.451282+0000 kernel: libceph: mon2 (2)172.30.233.144:3300 missing required protocol features
2024-08-13T05:16:58.451303+0000 kernel: libceph: mon2 (2)172.30.233.144:3300 session lost, hunting for new mon
2024-08-13T05:16:58.451321+0000 kernel: libceph: mon1 (2)172.30.248.126:3300 session established
2024-08-13T05:16:58.451343+0000 kernel: libceph: RADOS feature set mismatch: server's required > my supported 0x2f018fb87aa4aafe, missing 0x80000000
2024-08-13T05:16:58.451355+0000 kernel: libceph: mon1 (2)172.30.248.126:3300 missing required protocol features
Version-Release number of selected component (if applicable):



Ceph team mentioned that it was because of the `upmap-read` balancer mode which isn't supported by the kernel client.

(There was a recent change on the RADOS side which actually enforced this, see ceph/ceph#57776. Prior to 18.2.4 and 19.1.1 all sorts of incompatibility checks were missing in this area.)




How reproducible:


Steps to Reproduce:
1.Setup ODF 4.17.0.70. 
2.This sets the balancer mode to upmap-read
3.Try creation application pods using ceph-FS volume. 

Actual results: POD creation fails with error: 
 MountVolume.MountDevice failed for volume "pvc-99a88fc8-18bb-4c9f-9b17-619803be4721" : rpc error: code = Internal desc = an error (exit status 32) occurred while running mount args: [-t ceph 172.30.211.105:3300,172.30.248.126:3300,172.30.233.144:3300:/volumes/csi/csi-vol-59580dd3-824d-4d3f-b5df-1d2aae13829c/0a9fdeac-ffa6-4f02-b223-be8e0a622b2e /var/lib/kubelet/plugins/kubernetes.io/csi/openshift-storage.cephfs.csi.ceph.com/f4c977bb751a5bd86b137e853bec376625ce8faccee6b0e3e15c6a5120020a9e/globalmount -o name=csi-cephfs-node,secretfile=/tmp/csi/keys/keyfile-3526911127,mds_namespace=ocs-storagecluster-cephfilesystem,ms_mode=prefer-crc,read_from_replica=localize,crush_location=host:compute-2|rack:rack2,_netdev] stderr: unable to get monitor info from DNS SRV with service name: ceph-mon
2024-08-13T05:17:39.311+0000 7f74dea48000 -1 failed for service _ceph-mon._tcp
mount error: no mds (Metadata Server) is up. The cluster might be laggy, or you may not be authorized




Expected results: pod creation should be successful. 


Additional info: Issue started happening https://github.com/ceph/ceph/pull/57776 was merged.

Comment 4 Red Hat Bugzilla 2026-03-04 08:54:08 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.