Bug 1782743 - [GSS] Forcing RGW to listen to all interfaces
Summary: [GSS] Forcing RGW to listen to all interfaces
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Ceph-Ansible
Version: 3.3
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: z4
: 3.3
Assignee: Guillaume Abrioux
QA Contact: Vasishta
John Brier
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2019-12-12 09:28 UTC by Karun Josy
Modified: 2023-03-24 16:25 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-ansible-3.2.39-1.el7cp Ubuntu: ceph-ansible_3.2.39-2redhat1
Doc Type: Bug Fix
Doc Text:
.The radosgw_address variable can be set to 0.0.0.0 Previously, the default value for `radosgw_address` was `0.0.0.0`. If you did not change the default value from `0.0.0.0`, then `ceph-ansible` would fail validation. However, this is a valid value for RADOS Gateway. With this update to {product}, the default value was changed to `x.x.x.x`, so you can change the value to `0.0.0.0` and it will pass validation.
Clone Of:
Environment:
Last Closed: 2020-04-06 08:27:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph-ansible pull 4840 0 None closed defaults: change monitor|radosgw_address default value 2021-01-20 09:42:19 UTC
Github ceph ceph-ansible pull 4920 0 None closed defaults: change monitor|radosgw_address default value (bp #4840) 2021-01-20 09:42:19 UTC
Red Hat Product Errata RHBA-2020:1320 0 None None None 2020-04-06 08:27:42 UTC

Description Karun Josy 2019-12-12 09:28:10 UTC
* Description of problem:

In earlier ceph-ansible versions, we were able to use 0.0.0.0 as radosgw_address.
But in the latest version it fails with :
---
"msg": "[ceph2-osd1] Validation failed for variable: radosgw_address\n[ceph2-osd1] Reason: Either radosgw_address, radosgw_address_block or radosgw_interface must be provided\n[ceph2-osd1] Given value for radosgw_address: 0.0.0.0", 
---

One of our customer have a 2  RGW setup with 2 IPs x.x.x.51 and x.x.x.52 and a VIP  x.x.x.50 which they use as keepalived.

When they modify the conf file to either of these, this setup works fine.
----
rgw frontends = civetweb port=0.0.0.0:80 num_threads=512
rgw frontends = civetweb port=80 num_threads=512
----

Can they setup this using ceph-ansible with the latest version? As it looks like 0.0.0.0 usage is deprecated.  


* Version-Release number of selected component (if applicable):
ceph-ansible-3.2.4-1.el7cp.noarch

Comment 16 errata-xmlrpc 2020-04-06 08:27:06 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, 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-2020:1320


Note You need to log in before you can comment on or make changes to this bug.