Project

General

Profile

Bug #57931

RGW rgw_frontend_type field is not checked correctly during the spec parsing

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

Status:
Resolved
Priority:
Normal
Category:
cephadm/rgw
Target version:
-
% Done:

0%

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

Description

A spec with the following type for example:

rgw_frontend_type: "beast endpoint=10.16.96.54:8043 tcp_nodelay=1" 

Would be applied without any error message by cephadm however, in this case the SSL section is not parsed correctly and the user is not warned about that.


Related issues

Copied to Orchestrator - Backport #63011: quincy: RGW rgw_frontend_type field is not checked correctly during the spec parsing Resolved
Copied to Orchestrator - Backport #63012: reef: RGW rgw_frontend_type field is not checked correctly during the spec parsing Resolved

History

#1 Updated by Redouane Kachach Elhichou over 1 year ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 48630

#2 Updated by Adam King 12 months ago

  • Status changed from Fix Under Review to Resolved

#3 Updated by Mykola Golub 12 months ago

Adam, don't we want to backport this?

#4 Updated by Adam King 6 months ago

  • Status changed from Resolved to Pending Backport
  • Backport set to reef, quincy

#5 Updated by Backport Bot 6 months ago

  • Copied to Backport #63011: quincy: RGW rgw_frontend_type field is not checked correctly during the spec parsing added

#6 Updated by Backport Bot 6 months ago

  • Copied to Backport #63012: reef: RGW rgw_frontend_type field is not checked correctly during the spec parsing added

#7 Updated by Backport Bot 6 months ago

  • Tags set to backport_processed

#8 Updated by Adam King 14 days ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF