Project

General

Profile

Actions
Copy link

Feature #51618

closed

rgw_frontends configuration in config database not persistent

Added by Tobias Fischer almost 3 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Ceph - v16.2.4, Ceph - v16.2.5
Pull request ID:

Description

following config settings in mon config DB

client.rgw.default.rgw1.qwbeps     basic     rgw_frontends     beast port=80 ssl_port=443 ssl_certificate=config://rgw/cert/s3.clyso.cloud/crt ssl_private_key=config://rgw/cert/s3.clyso.cloud/key
client.rgw.default.rgw2.pdptyf     basic     rgw_frontends     beast port=80 ssl_port=443 ssl_certificate=config://rgw/cert/s3.clyso.cloud/crt ssl_private_key=config://rgw/cert/s3.clyso.cloud/key
client.rgw.default.rgw3.ivivlg     basic     rgw_frontends     beast port=80 ssl_port=443 ssl_certificate=config://rgw/cert/s3.clyso.com/crt ssl_private_key=config://rgw/cert/s3.clyso.com/key
client.rgw.default.rgw4.dbmxbw     basic     rgw_frontends     beast port=80 ssl_port=443 ssl_certificate=config://rgw/cert/s3.clyso.com/crt ssl_private_key=config://rgw/cert/s3.clyso.com/key

keeps getting changed to
client.rgw.default.rgw1.qwbeps     basic     rgw_frontends     beast port=80
client.rgw.default.rgw2.pdptyf     basic     rgw_frontends     beast port=80
client.rgw.default.rgw3.ivivlg     basic     rgw_frontends     beast port=80
client.rgw.default.rgw4.dbmxbw     basic     rgw_frontends     beast port=80

noticed it in v16.2.4 and just occured again after update to v16.2.5
maybe orchestrator keeps reverting my changes?
really annoying because this stops our services from running each time

Actions
Copy link

Also available in: Atom PDF