Excellent, thank you for your swift response Florian. Now we have the why, and need to figure out how.
For completeness could you provide the charm versions involved and information about any space bindings?
The charm makes an attempt at avoiding the many pitfalls of determining the correct FQDN to use by using the one the Open vSwitch init script populates the external_ids:hostname field in the database with on initial startup.
This should be used in the certificate request and it should be used to populate the external_ids:system-id field, which is what the `ovn-controller` process uses when identifying to the database.
The charm should also explicitly not request sans [0], but from your output it appears to have done so anyway.
Excellent, thank you for your swift response Florian. Now we have the why, and need to figure out how.
For completeness could you provide the charm versions involved and information about any space bindings?
The charm makes an attempt at avoiding the many pitfalls of determining the correct FQDN to use by using the one the Open vSwitch init script populates the external_ ids:hostname field in the database with on initial startup.
This should be used in the certificate request and it should be used to populate the external_ ids:system- id field, which is what the `ovn-controller` process uses when identifying to the database.
The charm should also explicitly not request sans [0], but from your output it appears to have done so anyway.
0: https:/ /github. com/openstack- charmers/ charm-layer- ovn/blob/ 244d88779f10eed 85d796d98ddfc67 8a64333ece/ lib/charms/ ovn_charm. py#L234- L242