Bug #2169: Selecting a different OpenStack tenant has no effect - Foreman

Actions

Copy link

Bug #2169

closed

Selecting a different OpenStack tenant has no effect

Added by Anonymous over 12 years ago. Updated over 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Daniel Lobato Garcia

Category:

Compute resources

Target version:

1.3.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Foreman 1.1 RC5
Ubuntu 12.04 Server x86_64

How to reproduce:

Add new compute resource
Select OpenStack as the provider
Click Load Tenants after entering an auth URL, username, password. If multiple tenants exist then the drop down list gets populated.
Select a different tenant than the one that is listed as the first choice and click Submit
Foreman seems to only create the compute resource with the tenant that it listed as the first choice and not the one that is selected. Editing the saved compute resource to select another tenant has no effect; Foreman reverts back to the first tenant.

Actions

Copy link

Updated by Andy Taylor almost 12 years ago

I am able to reproduce this in Foreman 1.2 on CentOS 6.4. Same steps to reproduce as Avtar.

Nothing much of interest in the logs, except that I've compared the tenant_id in the HostsController#create section with the actual ID of the tenant I'd selected in Openstack, and they match. So something is getting lost along the way by the looks of it.

Actions

Copy link

Updated by Ohad Levy almost 12 years ago

Description updated (diff)
Target version set to 1.3.0

Actions

Copy link

Updated by Andy Taylor almost 12 years ago

Quick update on this for anyone else affected: you can get around it by creating a new user in Openstack assigned only to the tenant you want to provision to, then create a new Openstack compute resource in Foreman assigned to that tenant.

Actions

Copy link