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 2377090

Summary:	[NFS-Ganesha] Ganesha attempts to start twice on standby node after active node reboot in HA deployment, causing IO disruption
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Manisha Saini <msaini>
Component:	Cephadm	Assignee:	Shweta Bhosale <shbhosal>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	bkunal, cephqe-warriors, gouthamr, ngangadh
Target Milestone:	---
Target Release:	9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-20.1.0-72	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-01-29 06:50:47 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:

Description Manisha Saini 2025-07-08 08:34:24 UTC

Description of problem:
======================

In a high-availability NFS-Ganesha cluster setup, when the active node is rebooted, the Ganesha process is expected to fail over and start cleanly on the standby node. However, the standby node attempts to start Ganesha twice. 
This results in IO operations being halt from NFS clients twice during the transition period (Ref BZ - https://bugzilla.redhat.com/show_bug.cgi?id=2375725).
This behavior defeats the purpose of seamless failover and impacts workloads relying on continuous availability.


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


How reproducible:
===============
Always


Steps to Reproduce:
=================
1. Set up a HA NFS-Ganesha cluster with two nodes: active and standby.
2. Create an NFS export and mount it on a client.
3. Perform continuous IO using dd.
4. Reboot the active Ganesha node.

Actual results:
=============
Ganesha service is attempted to be started twice on the standby node.
IO operations from clients experience delay during this window.


Expected results:
=============
Ganesha should be started only once on the standby node upon failover.
The failover should be clean, with minimal or no disruption to IO operations.

Additional info:

Comment 10 errata-xmlrpc 2026-01-29 06:50:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Red Hat Ceph Storage 9.0 Security and Enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2026:1536