Bug 2018245

Summary:	[RFE][cephadm] 5.0 allow ability to bind RGW to loopback address
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	James Poole <jpoole>
Component:	Cephadm	Assignee:	Redouane Kachach Elhichou <rkachach>
Status:	CLOSED ERRATA	QA Contact:	Mohit Bisht <mobisht>
Severity:	low	Docs Contact:	Eliska <ekristov>
Priority:	unspecified
Version:	5.0	CC:	adking, ekristov, kdreyer, mgowri, mobisht, rkachach, tserlin, vdas, vereddy
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	6.0
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-17.2.3-24.el9cp	Doc Type:	Bug Fix
Doc Text:	.The Ceph Object Gateway daemons now bind to loopback addresses correctly Previously, `cephadm` excluded loopback interfaces when looking for a valid IP address on a host to bind the Ceph Object Gateway daemon, thereby the daemons would not bind to the loopback addresses. With this fix, the Ceph Object Gateway daemons can be bound to loopback addresses by performing an explicit check. If a loopback interface is detected, the `127.0.0.1` address is used for IPv4 and `::1` is used for IPv6 as the loopback address.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-20 18:55:34 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:
Bug Depends On:
Bug Blocks:	2126050

Description James Poole 2021-10-28 15:42:10 UTC

Description of problem:
In RHCS 4 we were able to bind the RADOS gateway to localhost with "endpoint=127.0.0.1:8080" in ceph.conf for example. If we provide network of '127.0.0.0/8' in the server specification yaml the RADOS gateway fails to deploy. 

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

How reproducible:
Every time, see below

Steps to Reproduce:
1. Create RADOS gateway with the following yaml:
---
service_type: rgw
service_id: ceph.prod
service_name: rgw.ceph.prod
placement:
  count_per_host: 1
  label: rgw_prod
networks:
- 127.0.0.0/8
spec:
  rgw_frontend_port: 8080
  rgw_realm: prod
  rgw_zone: prod
2. ceph orch apply -i rgw-service.yml
3. See rgw.ceph.prod remains 0/1 in `ceph orch ls`

Actual results:
RADOS gateway fails to deploy

Expected results:
RADOS gateway deploys and bound to 127.0.0.1:8080

Additional info:

Comment 2 Ken Dreyer (Red Hat) 2022-07-29 18:51:59 UTC

Is 127.0.0.0/8 documented anywhere? Did you try 127.0.0.0/32 instead?

Comment 3 Redouane Kachach Elhichou 2022-08-24 10:02:17 UTC

Thanks for reporting the issue.

Is there any use-case in customer/production for this request?

Comment 11 Redouane Kachach Elhichou 2022-09-16 09:04:21 UTC

doc text updated.

Comment 13 Redouane Kachach Elhichou 2022-09-21 14:26:08 UTC

Hello Elisa,

The text is OK,

Thank you!
Redouane.

Comment 23 errata-xmlrpc 2023-03-20 18:55:34 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 Ceph Storage 6.0 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:1360