Project

General

Profile

Bug #51618

rgw_frontends configuration in config database not persistent

Added by Tobias Fischer 5 months ago. Updated 9 days ago.

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

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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

History

#1 Updated by Casey Bodley 5 months ago

  • Project changed from rgw to Orchestrator

#3 Updated by Tobias Fischer about 2 months ago

I tried your proposal and it worked. Thanks. But nevertheless it would be nice to be able to prevent automatic changes in ceph config db in the future ;)

#4 Updated by Sebastian Wagner about 1 month ago

  • Priority changed from Normal to Low

#5 Updated by Sebastian Wagner 9 days ago

Tobias Fischer wrote:

I tried your proposal and it worked. Thanks. But nevertheless it would be nice to be able to prevent automatic changes in ceph config db in the future ;)

Not yet sure if this would be the right approach. I'd rather focus on improving cephadm's automation here.

#6 Updated by Tobias Fischer 9 days ago

propably yes. but nevertheless i think a feature to block any atomatic changes in conf db would be nice to have. sometimes you may wish to have your config protected by any automated processes ;)

Also available in: Atom PDF