Bug 2324306

Summary:	In an nvmeof scale down scenario, if changing lb group for a namespace, it might not be reflected correctly on all GW nodes
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Aviv Caro <acaro>
Component:	NVMeOF	Assignee:	harika chebrolu <hchebrol>
Status:	VERIFIED ---	QA Contact:	Manohar Murthy <mmurthy>
Severity:	high	Docs Contact:	ceph-doc-bot <ceph-doc-bugzilla>
Priority:	unspecified
Version:	8.0	CC:	aindenba, bdavidov, bhkaur, bkunal, cephqe-warriors, gbregman, hchebrol, kjosy, lchernin, linuxkidd, pdhange, rpollack, tserlin, vumrao
Target Milestone:	---	Keywords:	External
Target Release:	8.0z2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-nvmeof-container-1.3.4-1	Doc Type:	Known Issue
Doc Text:	.Some namespaces are not visible after multiple gateway scale-downs Previously, in cases where multiple gateways underwent a scale-down procedure, if a lb group change occurred in the removed gateway, the namespace might not be visible to the initiators. As a result, the ana grp id of that namespace would be reported incorrectly by some of the gateways. With this fix, after a scale-down operation, stop and then restart the daemons that are showing the incorrect ana grp id.	Story Points:	---
Clone Of:		Environment:
Last Closed:		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:	2317218

Description Aviv Caro 2024-11-07 09:25:00 UTC

Description of problem:

If the number of gws is scaled down (e.g. a gw that was a part of the gw group is removed), and then if changing the lb group of the last namespace in the ana group that owned by the removed gw, the ana grp id of that namespace will be reported incorrectly by some of the gws. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:

The work around in this case is to stop and start the daemons that show that ana grp id incorrectly.