Project

General

Profile

Bug #1879

Foreman fails to acquire IP when using AWS VPC with private IP

Added by Romain Vrignaud over 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
1.3.0
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

When using VPC on AWS with only private IP, foreman fails to acquire the IP
as it only ask for public IP.
IMHO there should be a failover on private IP or a choice from user when creating host.

Related issues

Related to Foreman - Feature #1871: VPC support on EC2 computeClosed2012-09-19
Related to Foreman - Feature #1868: Foreman should ask which VPC to use when creating a new Instance on EC2Duplicate2012-09-17

Associated revisions

Revision beed05de (diff)
Added by Mark O'Shea over 9 years ago

fixes #1871, #1879 - add VPC support to EC2 compute resource

Based on patch from Romain Vrignaud <>

History

#1 Updated by Dominic Cleal over 9 years ago

  • Description updated (diff)
  • Status changed from New to Resolved
  • Target version set to 1.3.0
  • % Done changed from 0 to 100

Implemented in #1871 with the VPC functionality, via a dropdown menu on the network tab to choose the preferred IP address.

Also available in: Atom PDF