diff --git a/CHANGELOG.md b/CHANGELOG.md index 38585ad5556..b38ba24f7a3 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,3 +1,4 @@ +- Fixed the path to the certificates in proxy deployment - Fixed issue for third-party certificates during migration (bsc#1253350) - Explained how to generate the DB certificate for the upgrade of a 5.0 peripheral server (bsc#1248282) - Explained how to generate the proxy certificates on a peripheral server (bsc#1249425) diff --git a/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc b/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc index 05733993df0..1e850a6f876 100644 --- a/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc +++ b/modules/installation-and-upgrade/pages/container-deployment/uyuni/proxy-deployment-uyuni.adoc @@ -220,7 +220,7 @@ You can consider generated certificates as {productname} builtin (self signed) c + Depending on the choice then provide either path to signing CA certificate to generate a new certificate or path to an existing certificate and its key to be used as proxy certificate. + -The CA certificates generated on the server are stored in the [path]``/var/lib/containers/storage/volumes/root/ssl-build`` directory. +The CA certificates generated on the server are stored in the [path]``/var/lib/containers/storage/volumes/root/_data/ssl-build`` directory. + For more information about existing or custom certificates and the concept of corporate and intermediate certificates, see xref:administration:ssl-certs-imported.adoc[]. @@ -236,13 +236,8 @@ This archive needs to be made available on the Proxy container host. .Task: Copy the Proxy configuration -. Copy the files from the Server container to the Server host OS: -+ ----- -mgrctl cp server:/root/config.tar.gz . ----- -. Next copy the files from the Server host OS to the Proxy host: +. Copy the files to the Proxy host: + ---- scp config.tar.gz :/root