From 7ec7403e16d20cbf247dcd60c0dc2da3b868253c Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Wed, 10 Mar 2021 14:50:30 -0500 Subject: [PATCH] mgr/cephadm: fix beast private key config option This has always been broken. However, beast SSL will also accept a pem (cert + key) via the ssl_certificate option, so any existing non-broken users (if they exist) must be using that. Signed-off-by: Sage Weil --- src/pybind/mgr/cephadm/services/cephadmservice.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pybind/mgr/cephadm/services/cephadmservice.py b/src/pybind/mgr/cephadm/services/cephadmservice.py index fd5db81507f..2510e45afda 100644 --- a/src/pybind/mgr/cephadm/services/cephadmservice.py +++ b/src/pybind/mgr/cephadm/services/cephadmservice.py @@ -750,7 +750,7 @@ class RgwService(CephService): if spec.ssl: args.append(f"ssl_port={daemon_spec.ports[0]}") args.append(f"ssl_certificate=config://rgw/cert/{spec.service_name()}.crt") - args.append(f"ssl_key=config://rgw/cert/{spec.service_name()}.key") + args.append(f"ssl_private_key=config://rgw/cert/{spec.service_name()}.key") else: args.append(f"port={daemon_spec.ports[0]}") frontend = f'beast {" ".join(args)}' -- 2.39.5