Feature #51618: rgw_frontends configuration in config database not persistent - Orchestrator - Ceph

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:

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

Updated by Casey Bodley almost 3 years ago

Project changed from rgw to Orchestrator

Actions

Copy link

Updated by Sebastian Wagner over 2 years ago

I think this is solved by https://docs.ceph.com/en/latest/cephadm/services/rgw/#setting-up-https already

Actions

Copy link

Updated by Tobias Fischer over 2 years 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 ;)

Actions

Copy link

Updated by Sebastian Wagner over 2 years ago

Priority changed from Normal to Low

Actions

Copy link

Updated by Sebastian Wagner over 2 years 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.

Actions

Copy link

Updated by Tobias Fischer over 2 years 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 ;)

Actions

Copy link