Bug 2129112

Summary:	rook-ceph-tools is not using the same network settings as rook-ceph-operator
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Tomas Coufal <tcoufal>
Component:	ocs-operator	Assignee:	Santosh Pillai <sapillai>
Status:	CLOSED NOTABUG	QA Contact:	Neha Berry <nberry>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	mmuench, mparida, nigoyal, odf-bz-bot, sapillai, sostapov
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-07 06:26:46 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 Tomas Coufal 2022-09-22 14:30:22 UTC

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

We've been debugging an issue with networking to external ceph and we figured out that enabling ceph tools via `OSCInitialization` creates a rook-ceph-tools pod with completely different network settings than it is applied to rook-ceph-operator

Version of all relevant components (if applicable): 4.10.6 ODF on OCP 4.10.26

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

Partially, options for debugging networking issues are limited.

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

Use rook-ceph-operator directly for remote shell instead of rook-ceph-tools.

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

Can this issue reproducible?

Yes

Can this issue reproduce from the UI?

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

Steps to Reproduce:
1. Install ODF in external mode
2. Deploy ceph tools via OSCInitialization
3. Compare Pod YAMLs

Actual results:

See attached Pod manifests to compare.

Tools pod has `.spec.hostNetwork: true` and `.spec.dnsPolicy: ClusterFirstWithHostNet` while operator pod has `.spec.dnsPolicy: ClusterFirst`. This leads to vastly different behavior when tools pod is able to use host routing table while operator can't.

Expected results:

Network setting matches

Additional info:

Related to: https://bugzilla.redhat.com/show_bug.cgi?id=2129111

Comment 4 Santosh Pillai 2022-09-26 13:27:21 UTC

Moving to OCS operator component, since that is responsible for creating the tool box.

Comment 13 Malay Kumar parida 2023-08-07 06:26:46 UTC

Enabling ceph tool box in external mode is not actually a supported operation, And it's not at all required. Any ceph changes can be done by directly going to the RHCS cluster.
Reference-https://issues.redhat.com/browse/RHSTOR-4512