On Quincy (17.2.6) we are able to use per host RGW SSL certificates using:
```shell
echo "{{ host_ssl_crt }}" | ceph config-key set rgw/cert/{{ realmname }}/{{ zonename> }}{{ hostname }}.crt -i -
echo "{{ host_ssl_key }}" | ceph config-key set rgw/cert/{{ realmname }}/{{ zonename> }}{{ hostname }}.key -i -
```
Logging on 17.2.6 shows:
```
Aug 14 14:41:01 ceph-dev-gw2 radosgw[1373]: framework conf key: ssl_certificate, val: config://rgw/cert/_ Realmname _/_ Zonename _/ceph-dev-gw2.crt
Aug 14 14:41:01 ceph-dev-gw2 radosgw[1373]: framework conf key: ssl_private_key, val: config://rgw/cert/_ Realmname _/_ Zonename _/ceph-dev-gw2.key
```
On reef (18.2.0) this fails and the logging shows:
```
Aug 15 10:50:17 ceph-dev-gw2 radosgw[178335]: framework conf key: ssl_certificate, val: config://rgw/cert/$realm/$zone.crt
Aug 15 10:50:17 ceph-dev-gw2 radosgw[178335]: framework conf key: ssl_private_key, val: config://rgw/cert/$realm/$zone.key
```
Is this a regression or should we configure this in another was?
With kind regards,
Jeroen
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
