Project

General

Profile

Actions

Bug #6817

closed

Compute Profile not saving/using Security Groups for AWS VPC groups. EC2 groups work fine.

Added by Shawn LoPresto about 10 years ago. Updated about 6 years ago.

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

Description

Setting the Security groups in a compute profile is not working. Once changes are saved, revisiting the Compute Profile settings results in a lit of blank security groups. Trying to launch a new host using this profile will result in no rules being added unless you specifically add them at the time of launch. I am running Foreman 1.5.2 and the issue also existed in 1.5.1.


Related issues 1 (0 open1 closed)

Has duplicate Foreman - Bug #10321: Compute Profiles Still Lose Security Groups on SelectDuplicate04/29/2015Actions
Actions

Also available in: Atom PDF