Project

General

Profile

Actions
Copy link

Feature #57254

closed

RGW deployment should fail early if port number is already in use

Added by Redouane Kachach Elhichou over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
47758

Description

RGW deployment should fail at initial stage if Port number is already in use

>>>  Deploy daemon rgw.foo1.test ...
>>>  Verifying port 80 ...
>>>  Cannot bind to IP 0.0.0.0 port 80: [Errno 98] Address already in use
>>>  ERROR: TCP Port(s) ''80'' required for rgw already in use"'
>>>- '2021-11-25T09:46:40.427101Z service:rgw.foo1 [ERROR] "Failed while placing
Actions
Copy link
 #1

Updated by Adam King over 1 year ago

  • Tracker changed from Bug to Feature
  • Subject changed from RGW deployment should fail realy if port number is already in use to RGW deployment should fail early if port number is already in use
  • Status changed from New to In Progress
  • Pull request ID set to 47758
Actions
Copy link
 #2

Updated by Redouane Kachach Elhichou over 1 year ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #3

Updated by Redouane Kachach Elhichou over 1 year ago

  • Status changed from Fix Under Review to Closed
  • Assignee deleted (Redouane Kachach Elhichou)

Technically it should be possible to detect which ports are in use on all the nodes but there're more things to keep in mind when implementing this feature such as who is using these ports (it could be an instance of the same daemon) .. PR https://github.com/ceph/ceph/pull/47758 contains more details about potential issues to be solved.

Actions
Copy link

Also available in: Atom PDF