Bug #6817: Compute Profile not saving/using Security Groups for AWS VPC groups. EC2 groups work fine. - Foreman

Bug #6817

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

Added by Shawn LoPresto almost 8 years ago. Updated almost 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Swapnil Abnave

Category:

Compute resources - EC2

Target version:

1.15.0

Difficulty:

Triaged:

Bugzilla link:

1303896

Pull request:

https://github.com/theforeman/foreman/pull/4089

Fixed in Releases:

Found in Releases:

1.5.2

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

Associated revisions

Revision 891c47ba (diff)
Added by Swapnil Abnave about 5 years ago

Fixes #6817 - AWS VPC groups - show after saving

History

#1 Updated by Dominic Cleal almost 8 years ago

Category set to Compute resources - EC2

#2 Updated by Ashton Davis almost 8 years ago

A related behavior to this - it seems that the form doesn't do a pull for the selected security group in the list. When I open a compute profile or load one, the security group first selected in the list doesn't load into the selection form below it.