Feature #5999
closed
Support assigning public IP to Amazon EC2 host
Added by cristian falcas over 10 years ago.
Updated over 6 years ago.
Category:
Compute resources - EC2
|
|
Description
Hello,
When creating a new host on an amazon compute resource and choosing for the "Managed IP" Public, no real IP is assigned to the machine.
We are using VPCs and not EC2.
We have a "nat" role that should also use some awscli commands in order to configure itself. Because no real IP is assigned, those commands timeout and fail, so we need to manually add an IP and rerun puppet.
I didn't see anything relevant in the logs, so please let me know if you want anything from our side regarding this.
Best regards,
Cristian Falcas
- Category set to Compute resources
It's worth noting that the "Managed IP" is about which IP Foreman picks to try and contact the new VM on, rather than having any impact on how the VM is created and which IP it's allocated. I'm not sure how the latter works.
- Tracker changed from Bug to Feature
- Subject changed from on amazon compute resource, choosing public ip is not working to Support assigning public IP to Amazon EC2 host
Let's rephrase it as a feature request :)
- Has duplicate Feature #6818: Add Public IP option to AWS hosts added
- Category changed from Compute resources to Compute resources - EC2
- Related to Feature #3521: Assign a specific IP to an AWS instance inside a VPC added
- Status changed from New to Ready For Testing
- Target version set to 1.7.2
- Pull request https://github.com/theforeman/foreman/pull/1932 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 29
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by