Project

General

Profile

Actions

Bug #12837

closed

Security Groups not populated after selecting Subnet in New Host > Virtual Machine

Added by Jordan Snodgrass about 9 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
High
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In New Host > Virtual Machine, the list of Security Groups is not populated after selecting a subnet. I see the following in my console when selecting a subnet:

Uncaught TypeError: Cannot read property 'subnet-31727477' of null

This is in 1.10.0-RC3. It works fine on our 1.8.4 version of Foreman, so pretty sure it's not a config or IAM issue.

I am unable to provision new EC2 instances due to this bug.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #11840: EC2 "Security Groups" unpredictable drop-down behavior Duplicate09/16/2015Actions
Related to Foreman - Bug #6535: EC2 Security Groups - empty boxClosedStefan Goethals07/09/2014Actions
Actions #1

Updated by Ivan Necas about 9 years ago

  • Project changed from Foreman Remote Execution to Foreman
  • Category changed from Usability to Compute resources - EC2
Actions #2

Updated by Dominic Cleal about 9 years ago

  • Category deleted (Compute resources - EC2)
  • Translation missing: en.field_release deleted (63)
Actions #3

Updated by Dominic Cleal about 9 years ago

  • Category set to Compute resources - EC2
Actions #4

Updated by Dominic Cleal about 9 years ago

  • Related to Bug #11840: EC2 "Security Groups" unpredictable drop-down behavior added
Actions #5

Updated by Jordan Snodgrass almost 9 years ago

  • Related to Bug #6535: EC2 Security Groups - empty box added
Actions #6

Updated by Dominic Cleal almost 9 years ago

  • Status changed from New to Duplicate

Thanks for your comment in #6535 which will go out in 1.10.2, closing this one.

Actions

Also available in: Atom PDF