Thanks Jörn, it worked for cloudkitty, after applying the patch the deployment went well. But :
- I still can't access the web console :
An error occurred authenticating. Please try again later.
- in cloudkitty-processor.log I am still having :
2023-10-18 10:46:25.271 8106 WARNING keystoneauth.identity.generic.base [-] Failed to discover available identity versions when contacting
https://dinternal.cloud.domain.tld:35357. Attempting to parse version from URL.: keystoneauth1.exceptions.connection.SSLError: SSL exception connecting to https://
dinternal.cloud.domain.tld
:35357: HTTPSConnectionPool(host='
dinternal.cloud.domain.tld
', port=35357): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:897)'),))
When generating the self-signed certificate, I noticed that the process had generated :
- two haproxy certificates, one for the internet with the external FQDN and the second for internal communication with the local internal FQDN.
- It also generated a backend certificate, that contains only the IP addresses of the 03 controllers as Subject Alternate Names without any mention of the domain I am using, is this correct?
[root@rscdeployer ~]# openssl x509 -noout -text -in /etc/yogakolla/certificates/backend-cert.pem
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
1c:66:7e:37:85:cf:ca:1c:da:42:f6:f1:1f:dc:1e:97.....
Signature Algorithm: sha256WithRSAEncryption
Issuer: CN = KollaTestCA
Validity
Not Before: Oct 17 15:04:26 2023 GMT
Not After : Oct 15 15:04:26 2025 GMT
Subject: C = US, ST = NC, L = RTP, OU = kolla
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
.....
.....
e6:23:a4:7f:30:74:ac:0c:2d:22:00:95:b6:ab:20:
98:6b
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Subject Alternative Name:
IP Address:10.10.3.5, IP Address:10.10.3.9, IP Address:10.10.3.13
Signature Algorithm: sha256WithRSAEncryption
36:86:cb:b4:9a:fe:33:0d:ff:af:87:5e:00:9d:69:4e:32:21:
Regards.
