Back to bug 2166354

Who When What Removed Added
Benamar Mekhissi 2023-02-01 15:15:05 UTC Assignee srangana bmekhiss
CC bmekhiss
Nir Yechiel 2023-02-02 07:29:54 UTC Assignee bmekhiss vthapar
Status NEW ASSIGNED
CC nyechiel
Vishal Thapar 2023-02-06 07:31:54 UTC Flags needinfo?(prsurve) needinfo?(bmekhiss)
Pratik Surve 2023-02-06 08:04:29 UTC Flags needinfo?(prsurve)
Benamar Mekhissi 2023-02-06 12:48:06 UTC CC vthapar
Flags needinfo?(bmekhiss) needinfo?(vthapar)
Benamar Mekhissi 2023-02-06 12:53:27 UTC Flags needinfo?(vthapar)
Karolin Seeger 2023-02-07 07:53:10 UTC CC kseeger
Vishal Thapar 2023-02-07 10:47:42 UTC Flags needinfo?(prsurve)
Vishal Thapar 2023-02-08 06:16:05 UTC Flags needinfo?(vthapar) needinfo?(vthapar)
Sunil Kumar Acharya 2023-03-19 17:58:34 UTC Flags needinfo?(vthapar)
Vishal Thapar 2023-04-05 05:21:01 UTC Flags needinfo?(prsurve) needinfo?(vthapar) needinfo- needinfo-
Vishal Thapar 2023-04-05 05:28:41 UTC Doc Type If docs needed, set a value Known Issue
Doc Text Cause:
Endpointslices synced to broker don't use source namespace and are stored in broker namespace. When two different clusters export same service name but different namespace only one of them can exist in broker namespace

Consequence:
Only one Endpointslice will be synced to remote cluster. As different clusters try to keep syncing their endpointslices, one in broker keeps flipping to service from different clusters. Depending on which EPSlice is currently synced, DNS queries for one not synced will fail.

Workaround (if any):
Don't use same service name but different namespace when exporting service in different clusters. If it is essentially same service, use same namespace. If not, use a different service name.

Result:
Queries to one of the service can intermittently fail.
Raghavendra Talur 2023-07-10 04:45:53 UTC CC rtalur
Summary [RDR][CEPHFS] sync/replication is getting stopped for some pvc rsync: connection unexpectedly closed [RDR][CEPHFS][Tracker] sync/replication is getting stopped for some pvc rsync: connection unexpectedly closed
Red Hat Bugzilla 2023-08-03 08:30:43 UTC CC ocs-bugs
Elad 2023-08-09 17:00:43 UTC CC odf-bz-bot

Back to bug 2166354