Problem: We’re running into issues or inconsistencies with provisioning using the Openstack plugin. The Compute Resource profile takes a tenant or project name as part of it’s default configuration, but the build options for a new VM list all of the available tenants / projects that the resource has access to, and this appears to have no actual effect on the creation, and the VM is created in the default project where the compute resource seems to be scoped.
Similar to Bug #23517: Openstack Multi Tenant Project inconsistencies - Foreman
Expected outcome:. The compute resource is able to be provisioned in any project the user has access to, and the tokens are scoped properly to either domain or project accordingly
Foreman and Proxy versions: 3.1.3
Foreman and Proxy plugin versions: 3.1.3
Distribution and version: CentOS 7
Other relevant data: