Project

General

Profile

Actions

Bug #31555

open

foreman-compute-ec2 fail to associate hosts

Added by Danie de Jager over 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - EC2
Target version:
-
Difficulty:
medium
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

I see the IP shown by foreman-compute-ec2 under Compute resources is only one IP of the assigned 5 to the host, the highest value. We have hosts with IP allocated to hosts but not assigned the the host itself yet to allow for projects that still need to go live.

Therefore on the host I have IP assigned by running ip -a
10.0.1.1
10.0.1.2
10.0.1.3
10.0.1.4
but not
10.0.1.5

For some reason the Compute Resource I want to associate is using the highest/last IP on the list (10.0.1.5) of assigned IP in the AWS EC2 console. Therefore I cannot assign the EC2 host to an existing host on Foreman.

I went so far as to add a new Virtual NIC under the existing host's primary NIC with the 10.0.1.5 IP but that still did not allow me to associate the EC2 with the existing host.

Will it not be better if the EC2 compute resource uses the lowest IP count as the primary IP?

Actions

Also available in: Atom PDF