Fix the ssl-build path in proxy deployment (#4571)

cbosdo · web-flow · commit 7435aa414e03 · 2025-12-11T11:33:19.000+01:00
* Fix the ssl-build path in proxy deployment
* Remove useless steps in uyuni proxy deployment page
diff --git 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
@@ -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 <proxy-FQDN>:/root

Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,4 @@`
	`1`	`+- Fixed the path to the certificates in proxy deployment`
`1`	`2`	`- Fixed issue for third-party certificates during migration (bsc#1253350)`
`2`	`3`	`- Explained how to generate the DB certificate for the upgrade of a 5.0 peripheral server (bsc#1248282)`
`3`	`4`	`- Explained how to generate the proxy certificates on a peripheral server (bsc#1249425)`
Original file line number	Diff line number	Diff line change
`@@ -220,7 +220,7 @@ You can consider generated certificates as {productname} builtin (self signed) c`
`220`	`220`	`+`
`221`	`221`	`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.`
`222`	`222`	`+`
`223`		-The CA certificates generated on the server are stored in the [path]``/var/lib/containers/storage/volumes/root/ssl-build`` directory.
	`223`	+The CA certificates generated on the server are stored in the [path]``/var/lib/containers/storage/volumes/root/_data/ssl-build`` directory.
`224`	`224`	`+`
`225`	`225`	`For more information about existing or custom certificates and the concept of corporate and intermediate certificates, see xref:administration:ssl-certs-imported.adoc[].`
`226`	`226`
`@@ -236,13 +236,8 @@ This archive needs to be made available on the Proxy container host.`
`236`	`236`
`237`	`237`
`238`	`238`	`.Task: Copy the Proxy configuration`
`239`		`-. Copy the files from the Server container to the Server host OS:`
`240`		`-+`
`241`		`-----`
`242`		`-mgrctl cp server:/root/config.tar.gz .`
`243`		`-----`
`244`	`239`
`245`		`-. Next copy the files from the Server host OS to the Proxy host:`
	`240`	`+. Copy the files to the Proxy host:`
`246`	`241`	`+`
`247`	`242`	`----`
`248`	`243`	`scp config.tar.gz <proxy-FQDN>:/root`