← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1364659] Re: [HEAT] It's impossible to assign 'default' security group to node group

 

** Also affects: horizon
   Importance: Undecided
       Status: New

** Summary changed:

- [HEAT] It's impossible to assign 'default' security group to node group
+ [Sahara][HEAT engine] It's impossible to assign 'default' security group to node group

** Changed in: horizon
     Assignee: (unassigned) => Andrew Lazarev (alazarev)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1364659

Title:
  [Sahara][HEAT engine] It's impossible to assign 'default' security
  group to node group

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Data Processing (Sahara, ex. Savanna):
  In Progress

Bug description:
  Steps to repro:
  1. Use HEAT provisioning engine
  2. Login as admin user who has access to several tenants
  3. Create node group template with 'default' security group assigned
  4. Create cluster with this node group

  Expected result: cluster is created
  Observed result: Cluster in error state. Heat stack is in state {"stack_status_reason": "Resource CREATE failed: PhysicalResourceNameAmbiguity: Multiple physical resources were found with name (default).",  "stack_status": "CREATE_FAILED"}

  Problem investigation:
  Heat searches security group name in all tenants accessible for user, not only in tenant where stack is going to be created (heat bug?).

  Steps to make things better:
  1. We can allow specifying security group with ID
  2. Horizon UI can use IDs instead of names for security groups

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1364659/+subscriptions