Project

General

Profile

Actions

Bug #12620

closed

Foreman fails to display AWS EC2 security groups on host provision

Added by Matt Darcy over 8 years ago. Updated about 8 years ago.

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

Description

when building a new host with the EC2 compute resource, when the security groups dialog is presented, the list is totally empty. This makes it impossible to select a security group from your host and forces a security risk, to work around being unable to select a security group, the default security group must be configured to allow foreman access on ssh and puppet or builds will fail, you then need to go into the AWS console and manually change the security group for the new host, which adds manual tasks to provisioning, and raises questions from support groups about the use of foreman.

this bug is in 1.9.3 and is present in my current test system build of 1.10-RC3

On occasion if you build the host, re-visit the host and click "edit" against the host, the security groups dialog will be populated, but this is very rare, and useless unless the above default security group compromise configuration has been implemented !


Files

foreman-security-grops-bug.png View foreman-security-grops-bug.png 365 KB screen shot of foreman 1.10-rc3 lacking security groups Matt Darcy, 11/27/2015 04:22 AM

Related issues 1 (0 open1 closed)

Related to Foreman - Bug #11840: EC2 "Security Groups" unpredictable drop-down behavior Duplicate09/16/2015Actions
Actions #2

Updated by Dominic Cleal over 8 years ago

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

Updated by Dominic Cleal about 8 years ago

  • Status changed from New to Duplicate

Thanks for the report. I believe this has been fixed in #6535 due to be released in Foreman 1.10.2.

Actions

Also available in: Atom PDF