Project

General

Profile

Bug #3133

Can't assign Security group to EC2 instance when creating host

Added by Alejandro Falcon about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Compute resources
Target version:
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Creating a new EC2 host doesn't have the option to assign it to a security group.

Associated revisions

Revision 68522ec8 (diff)
Added by Dominic Cleal about 9 years ago

fixes #3133 - fix security group filtering when no groups need filtering

Revision 1f3f25f9 (diff)
Added by Dominic Cleal about 9 years ago

fixes #3133 - fix security group filtering when no groups need filtering

(cherry picked from commit 68522ec81c0b64df5306165f4e1be95728158600)

History

#1 Updated by Alejandro Falcon about 9 years ago

Host is assigned to Default sec group by default.

#2 Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Feedback

It moved to the Network tab as we added VPC support too, can you check there please?

#3 Updated by Alejandro Falcon about 9 years ago

I can only see Domain and Managed IP (btw what does it mean?) under network tab.

#4 Updated by Dominic Cleal about 9 years ago

Do you have any VPCs on your EC2 account? I wonder if this is a regression for the case where there aren't any.

#5 Updated by Dominic Cleal about 9 years ago

  • Related to Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final added

#6 Updated by Alejandro Falcon about 9 years ago

No, I don't use VPC at all.

#7 Updated by Dominic Cleal about 9 years ago

  • Status changed from Feedback to New

Thanks for the report, I can reproduce now this after deleting my VPC.

#8 Updated by Dominic Cleal about 9 years ago

  • Priority changed from High to Urgent

#9 Updated by Dominic Cleal about 9 years ago

Alejandro Falcon wrote:

I can only see Domain and Managed IP (btw what does it mean?) under network tab.

It essentially means which IP Foreman will try to connect to in order to complete the provisioning process, by running the finish script over SSH. Depends where the Foreman instance is in relation to the VM on the network.

#10 Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Dominic Cleal

#11 Updated by Dominic Cleal about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#12 Updated by Lukas Zapletal about 9 years ago

  • Related to deleted (Tracker #3112: [TRACKER] Issues to be released in 1.3 RC or final)

Also available in: Atom PDF