To Reproduce Steps to reproduce the behavior:

1. Create an OpenStackVersion with name X
2. Create an OpenStackControlPlane with name Y
3. View the OpenStack operator controller-manager logs and see that it tries to create a second OpenStackVersion, errors out and blocks further reconciliation

Expected behavior

• The OpenStack operator controller-manager should find the existing OpenStackVersion CR and use that instead of trying to create a new one, regardless of what name the OpenStackVersion might have, OR we should prevent divergent resource names in the first place and inform the user of the problem when it is detected.

Known workaround

• If you need to create a custom OpenStackVersion, make sure to give it the same name as you give your OpenStackControlPlane
• Or, if you don't need a custom OpenStackVersion, just let the operator create it automatically during OpenStackControlPlane reconciliation