Project

General

Profile

Bug #10321

Compute Profiles Still Lose Security Groups on Select

Added by Shawn LoPresto over 7 years ago. Updated over 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Looks like this issue still exists in 1.8. I am able to see my security groups just fine and even add the proper groups to each compute profile.

When creating a new host and selecting the compute profile, the security groups are blank. I have to change the subnet selection forward/back to get the rules to show up at all. So there are two issues that may be related.

1. Groups not propagated to new host after profile selection during launch.

To reproduce, just make a compute profile with your selection and then try launching a new host with that profile.

2. When the results from #1 are not returned, you get a blank set of rules for that subnet until you toggle subnets.


Related issues

Is duplicate of Foreman - Bug #6817: Compute Profile not saving/using Security Groups for AWS VPC groups. EC2 groups work fine.Closed2014-07-29

History

#1 Updated by Dominic Cleal over 7 years ago

  • Is duplicate of Bug #6817: Compute Profile not saving/using Security Groups for AWS VPC groups. EC2 groups work fine. added

#2 Updated by Dominic Cleal over 7 years ago

  • Status changed from New to Duplicate
  • Legacy Backlogs Release (now unused) deleted (50)

Tracked under your original report, #6817.

Also available in: Atom PDF