Project

General

Profile

Actions

Bug #2169

closed

Selecting a different OpenStack tenant has no effect

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

Status:
Closed
Priority:
Normal
Category:
Compute resources
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Foreman 1.1 RC5
Ubuntu 12.04 Server x86_64

How to reproduce:
  1. Add new compute resource
  2. Select OpenStack as the provider
  3. Click Load Tenants after entering an auth URL, username, password. If multiple tenants exist then the drop down list gets populated.
  4. Select a different tenant than the one that is listed as the first choice and click Submit
  5. 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 #1

Updated by Andy Taylor almost 11 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 #2

Updated by Ohad Levy almost 11 years ago

  • Description updated (diff)
  • Target version set to 1.3.0
Actions #3

Updated by Andy Taylor almost 11 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 #4

Updated by Daniel Lobato Garcia almost 11 years ago

  • Assignee set to Daniel Lobato Garcia
Actions #5

Updated by Dominic Cleal almost 11 years ago

  • Status changed from New to Ready For Testing
Actions #6

Updated by Daniel Lobato Garcia almost 11 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF