Actions
Bug #6817
closed
Compute Profile not saving/using Security Groups for AWS VPC groups. EC2 groups work fine.
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - EC2
Target version:
Difficulty:
Triaged:
Bugzilla link:
Pull request:
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.
Updated by Dominic Cleal over 10 years ago
- Category set to Compute resources - EC2
Updated by Ashton Davis over 10 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.
Updated by Andy Taylor over 9 years ago
I'm seeing this problem in Foreman 1.7.3 as well.
Updated by Dominic Cleal over 9 years ago
- Has duplicate Bug #10321: Compute Profiles Still Lose Security Groups on Select added
Updated by
Updated by The Foreman Bot almost 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4089 added
Updated by Swapnil Abnave over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 891c47ba49818dab042de7c090a2b6a9e5418d24.
Updated by Dominic Cleal over 7 years ago
- Translation missing: en.field_release set to 209
Actions