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 2379520

Summary: [BYOK] [RFE]Cephadm NFS service spec does not support per-host KMIP port configuration
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Manisha Saini <msaini>
Component: CephadmAssignee: Shweta Bhosale <shbhosal>
Status: CLOSED UPSTREAM QA Contact: Vinayak Papnoi <vpapnoi>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.1CC: akane, ben.kern, bluitel, cephqe-warriors, ngangadh, sabose, tserlin
Target Milestone: ---Keywords: External, FutureFeature
Target Release: 9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-20.1.0-14 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2392399 (view as bug list) Environment:
Last Closed: 2026-03-04 09: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: 2394541    
Bug Blocks: 2392399    

Description Manisha Saini 2025-07-11 10:49:35 UTC
Description of problem:
===============

The KMIP block in the NFS-Ganesha configuration allows specifying both addr and port for each KMIP HOST. This is necessary in scenarios like IBM Cloud, where different KMIP endpoints may operate on non-default ports. However, the cephadm does not currently support specifying port per host in the NFS service spec.


Version-Release number of selected component (if applicable):
================================
# ceph --version
ceph version 19.2.1-234.el9cp (abe90cadf4fae6d213cb75dab705ca8e05ac1210) squid (stable)

How reproducible:
=============
N/A


Steps to Reproduce:
============

1. Attempt to deploy an NFS-Ganesha service with BYOK support using cephadm and the following kind of service spec:

service_type: nfs
service_id: ganesha
spec:
  ...
  kmip_host:
    - addr: host1
      port: 15696
    - addr: host2
      port: 999
  ...

2. Apply the service spec using ceph orch apply -i spec.yaml


Actual results:
============
KMIP configuration defaults to port 5696 for all hosts, which may not match actual KMIP server configuration.


Expected results:
==============
Cephadm should accept and parse the port field along with addr in the KMIP host list in the NFS service spec.Pass this configuration to NFS-Ganesha correctly.


Additional info:

Comment 4 ben.kern 2025-07-15 00:29:41 UTC
In order to support an ingress endpoint, ganesha will need to communicate to list of ips defined in the ganesha conf over port 443 (default ingress port) and specify a servername in the ssl config.

Each IP will be expected to have the same port and same servername if that makes the config any easier. Essentially allowing to connect to a custom endpoint with an SNI override.

Comment 14 Binod Luitel 2025-10-15 13:36:38 UTC
We have verified the latest z2 version have the configurable port. Thanks. This issue is resolved.

Comment 16 Red Hat Bugzilla 2026-03-04 09:54:08 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.