This looks like a smooth upgrade, nothing major changed and everything seem to work. However, there is one slight detail - fog-openstack URL is not versionless, therefore it must not contain any path part (/v2 or /v3) as the API code determines the version from the other fields. This is the upstream change:

• https://github.com/fog/fog-openstack/commit/bfb27375e5590e3f2a462c79a96a7b16ca0c421b

Keystone endpoints are version less. Version 3 is the default as v2.0 is deprecated. Meanwhile Keystone V3 still supports v2.0 for backward compatibility. Therefore passing a tenant instead of a project (along with a domain) makes Keystone provide v2.0 token.

This does not work nicely with Foreman when Tenants are not known (before Load tenants button is pressed), therefore the easiest solution is to enforce users to select V2 or V3. Instead adding new flag, I propose easier approach which will be also upgrade-friendly - Compute Resource model now validates if URL contains /v2 or /v3 and this is used to pick either v2.0 or v3 protocol. Users already have paths so this will work transparently for them.