When implementing this change with config-flags, the implementation of config-flags seems to have failed to create a new section per the config-flags definition:
The /etc/ceph/config file has the following three extra lines from this config change:
# The following are user-provided options provided via the config-flags charm option.
# User-provided [client.radosgw.gateway] section config
rgw_relaxed_s3_bucket_names = true
Expected result would be these two lines (plus any juju comments):
[client.radosgw.gateway]
rgw_relaxed_s3_bucket_names = true
Note the lack of DEFINING the [client.radosgw.gateway] section of the file.
When implementing this change with config-flags, the implementation of config-flags seems to have failed to create a new section per the config-flags definition:
juju config ceph-radosgw config- flags=' {"client. radosgw. gateway" : {"rgw_relaxed_ s3_bucket_ names": "true"}}'
The /etc/ceph/config file has the following three extra lines from this config change:
# The following are user-provided options provided via the config-flags charm option. radosgw. gateway] section config s3_bucket_ names = true
# User-provided [client.
rgw_relaxed_
Expected result would be these two lines (plus any juju comments): radosgw. gateway] s3_bucket_ names = true
[client.
rgw_relaxed_
Note the lack of DEFINING the [client. radosgw. gateway] section of the file.
root@juju- 733f2f- 4-lxd-12: /etc/ceph# grep '\[' ceph.conf rgw.juju- 733f2f- 4-lxd-12] radosgw. gateway] section config
[global]
[client.
# User-provided [client.