Self Signed Certs Cause Metadata cert errors seemingly

Bug #2054404 reported by Noel Ashford
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Invalid
Undecided
Unassigned
kolla
New
Undecided
Unassigned

Bug Description

==> /var/log/kolla/nova/nova-metadata-error.log <==
2024-02-18 00:58:15.029954 AH01909: tunninet-server-noel.ny5.lan.tunninet.com:8775:0 server certificate does NOT include an ID which matches the server name
2024-02-18 00:58:16.360069 AH01909: tunninet-server-noel.ny5.lan.tunninet.com:8775:0 server certificate does NOT include an ID which matches the server name

I have no cert issues elsewhere, just this. What could cause this? it usually elsewhere has an IP and the fqdn as SAN's.

How can i troubleshoot the root cause ?

Revision history for this message
Sylvain Bauza (sylvain-bauza) wrote :

Doesn't look to me a Nova bug, maybe a Kolla one. Moving this report then.

Changed in nova:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.