Project

General

Profile

Actions

Bug #39321

closed

rgw: Beast frontend listens on IPv4 only by default

Added by Wido den Hollander about 5 years ago. Updated almost 5 years ago.

Status:
Duplicate
Priority:
High
Target version:
-
% Done:

0%

Source:
Tags:
rgw,beast,ipv6
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

rgw_frontends = "beast"

This leads to the RGW to bind on 0.0.0.0:80 as shown by ss:

State       Recv-Q Send-Q                                                            Local Address:Port                                                                           Peer Address:Port              
LISTEN      0      128                                                                           *:80                                                                                        *:*                   users:(("radosgw",pid=537897,fd=133))
rgw_frontends = "beast endpoint=[::]:80"

This makes RGW listen on both IPv4 and IPv6, but the default should imho be to listen on v4 and v6.

Tested this with Mimic 13.2.5


Related issues 1 (0 open1 closed)

Is duplicate of rgw - Bug #39038: beast: multiple v4 and v6 endpoints with the same port will cause failure ResolvedAbhishek Lekshmanan03/29/2019

Actions
Actions #1

Updated by Nathan Cutler about 5 years ago

  • Project changed from Ceph to rgw
Actions #3

Updated by Casey Bodley about 5 years ago

  • Status changed from New to 12
  • Priority changed from Normal to High
Actions #4

Updated by Casey Bodley almost 5 years ago

  • Status changed from 12 to In Progress
  • Assignee set to Abhishek Lekshmanan
Actions #6

Updated by Casey Bodley almost 5 years ago

  • Is duplicate of Bug #39038: beast: multiple v4 and v6 endpoints with the same port will cause failure added
Actions #7

Updated by Casey Bodley almost 5 years ago

  • Status changed from In Progress to Duplicate
Actions

Also available in: Atom PDF