Would it be possible to
remove the enumeration of openstack extensions when stopping a VM?
Some hosting providers don't support the API endpoint that allows you to enumerate the available extensions-- I'm working with one of those providers.
It seems that openstack extensions are only required to stop the intermediate VM and for finding flavor ref based on flavor name. In my case, the provider supports stopping the VM through the API, despite not allowing you to discover that you can stop the VM. Instead of attempting to discover the extension and aborting if that extension isn't supported, attempt a best-effort to stop the VM and inform the user or otherwise handle this through the existing "failed to stop the VM" flow?
TBH, I hate that this problem exists and dislike the solution, but since there is already error handling around stopping the server, I don't think the impact will be that great. Also, I suspect that it's a very (very) small population of openstack servers that won't support stopping a server via API. I can prepare a very simple PR if you all don't burn me at the stake for the suggestion.
Reference links: