Bug #31555
openforeman-compute-ec2 fail to associate hosts
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?
Updated by Tomer Brisker over 4 years ago
- Category set to Compute resources - EC2
Updated by Danie de Jager over 4 years ago
- Category deleted (
Compute resources - EC2)
I had to take the IP from "Private ip address" under the EC2 Compute Resouce VM and go to the existing host name and edit it. I had to edit the NIC and tick primary on the Virtual NIC where the IP matched the IP under EC2. Then the associate VMs button found and attached to the exiting host.
I would recommend that it uses the hosts lowest IP and not the highest as the primary should always be the lowest IP and almost never be the highest IP.
Updated by Tomer Brisker over 4 years ago
- Category set to Compute resources - EC2
Updated by Amir Fefer almost 4 years ago
- Difficulty set to medium
- Triaged changed from No to Yes
Repreduced
I also had an issue with associate an host with EC2