Bug 2193220

Summary:	[Stretch cluster] CephCluster is updated frequently due to changing ordering of zones
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Travis Nielsen <tnielsen>
Component:	ocs-operator	Assignee:	Malay Kumar parida <mparida>
Status:	CLOSED ERRATA	QA Contact:	Mahesh Shetty <mashetty>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	mashetty, ocs-bugs, odf-bz-bot, srai, tdesala
Target Milestone:	---	Keywords:	Regression, TestBlocker
Target Release:	ODF 4.13.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.13.0-184	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-06-21 15:25:37 UTC	Type:	---
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:	2187952

Description Travis Nielsen 2023-05-04 18:13:43 UTC

This bug was initially created as a copy of Bug #2187952

I am copying this bug because: 



Description of problem (please be detailed as possible and provide log
snippests):

Hi, when we try to deploy vSphere UPI stretch cluster arbiter cluster with latest ODF 4.13-168 builds, there seems to be some issue with rook-ceph-operator pod and the deployments are failing to complete. rook-ceph-operator-* pod is in CrashLoopBackOff state with following error:

Last State:     Terminated
      Reason:       Error
      Message:      failed to run operator: gave up to run the operator manager: failed to set up overall controller-runtime manager: error listening on :8080: listen tcp :8080: bind: address already in use
      Exit Code:    1




Version of all relevant components (if applicable):
ODF 4.13-168

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
yes

Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:
yes

Steps to Reproduce:
1. Deploy stretch cluster with arbiter using latest ODF 4.13 builds
2. 
3.


Actual results:
Deployments are failing

Expected results:
Deployments should succeed

Additional info:

Live-cluster: http://magna002.ceph.redhat.com/ocsci-jenkins/openshift-clusters/mashetty-s1/mashetty-s1_20230419T042248/openshift-cluster-dir/auth/kubeconfig

Comment 8 Malay Kumar parida 2023-05-08 12:36:06 UTC

For a solution, I have tried to keep the array of values for a topology map label always sorted, Which will help us avoid frequently updating the CR with the same values in a different order.

Comment 15 errata-xmlrpc 2023-06-21 15:25:37 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 (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix 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/RHBA-2023:3742