Hi Julio, I am getting the same error. This is with a new install of Uyuni 2022.02. It looks like the certificate is getting created in /root/ssl-build but the rpm package is not. I manually copied the certificate and key to the locations in /etc/pki/tls/ indicated by the apache2 config to be able to start the web service, but we need to build the cert rpm package for deployment to clients. We're actually going to go through the procedure to build a custom CA-signed cert so we will see whether that goes OK or if it breaks as well, but the default process for using a self-signed cert seems to be broken after the creation of the cert. The self signed cert also appears to have the OU and O order mixed up, although I expect that shouldn't be enough to break the cert configuration. Cheers, Paul-Andre Panon
In retrospect, the problem may be that we actually entered a password for the private key. That seems to have been OK for the self-signed cert generation but is probably what broke subsequent steps in rpm package generation. From: Paul-Andre Panon Sent: Monday, March 28, 2022 12:30 PM To: users@lists.uyuni-project.org Subject: RE: Set up Uyuni with YaST ERROR Hi Julio, I am getting the same error. This is with a new install of Uyuni 2022.02. It looks like the certificate is getting created in /root/ssl-build but the rpm package is not. I manually copied the certificate and key to the locations in /etc/pki/tls/ indicated by the apache2 config to be able to start the web service, but we need to build the cert rpm package for deployment to clients. We're actually going to go through the procedure to build a custom CA-signed cert so we will see whether that goes OK or if it breaks as well, but the default process for using a self-signed cert seems to be broken after the creation of the cert. The self signed cert also appears to have the OU and O order mixed up, although I expect that shouldn't be enough to break the cert configuration. Cheers, Paul-Andre Panon
participants (1)
-
Paul-Andre Panon