Bug #3513
open
Foreman assigns wrong VPC when multiple VPCs have same subnets
Added by Jim Bailey about 11 years ago.
Updated over 10 years ago.
Category:
Compute resources - EC2
|
|
Description
If you have multiple VPCs with the same subnets, for example a dev, test and live VPC. Foreman does not allow you to select the VPC you need. Instead it assigns you to a VPC based on some internal logic.
This means that Foreman provisioning on ec2 is broken where subnets are reused within differnet VPCs.
Related issues
1 (1 open — 0 closed)
Just attempted some more provisioning inside VPCs sharing the same subnet layout it appears to be random as to which VPC foreman assigns the instance to. The functionality to select VPCs is available in Fog, as is the ability to select an specific IP from that subnet. However this functionality is not exposed by the Foreman UI or API.
Using a restricted IAMs as suggest on list doesn't help it still randomly assigns the VPC which if it assigns to the wrong VPC results in an IAMs permission denied rather than an inaccessible instance in the wrong VPC.
- Related to Bug #6787: Turn off the validation on ip addresses added
- Category changed from Compute resources to Compute resources - EC2
Also available in: Atom
PDF
Updated by 
Updated by