Project

General

Profile

Actions
Copy link

Bug #1879

closed

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

Added by Romain Vrignaud about 12 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Compute resources
Target version:
1.3.0
Difficulty:
Triaged:
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 2 (0 open — 2 closed)

Related to Foreman - Feature #1871: VPC support on EC2 computeClosed09/19/2012Actions
Related to Foreman - Feature #1868: Foreman should ask which VPC to use when creating a new Instance on EC2Duplicate09/17/2012Actions
Actions
Copy link
 #1

Updated by Dominic Cleal about 11 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.

Actions
Copy link

Also available in: Atom PDF