Bug #7244
closed
DHCP priority messup with Ovirt Second Nic through Foreman
Description
I'm facing the following problem:
When creating a host using FM in oVirt gives me trouble with a second nic and it's mac(priority) with dhcp/building/finish:
When I create a host with 2 nics using FM at once I get:
Mixed up Nics/Networks, Nic1 has the Network of Nic2 and the other way around.
- I need to change this manually to get a DHCP address on the first nic while booting, the install goes right but it cannot finish due the wrong mac-address on the wrong IP.
- Completed 405 Method Not Allowed in the Production Log
When I create a host with 1 nic using FM and adding the secondone later on manually in ovirt and Foreman (environment update is on false due a bug):
- The first nic doesn't get IP, the second one get's one.
- The installer starts, tries to get DHCP but cannot get any
I'm not sure why this happens and why the MAC priority of NIC2 is higher (lower in number) than NIC1
Files
Updated by Yama Kasi over 10 years ago
I forgot to ask/mention that the installer only DHCP's the first Nic, so the lowest priority which will be Nic2 instead of Nic1.
This wouldn't be an issue on one large network, as both are vlanned this won't work and shouldn't be the right setup anyway.
Waht about that one Nic DHCP for the installer.
Updated by Yama Kasi over 10 years ago
This could be related to ovirt Mac-addressing, mailing them to the mailinglist.
Updated by Yama Kasi over 10 years ago
- File wrong nic boot.PNG wrong nic boot.PNG added
Small update on this with a screenshot.
This happens with a New host where all nics are added through foreman. It seems that oVirt uses wrong mac's that don't higher up well. It's in a way in the pool that I can't get it out.
Nic1: 00:1a:4a:a8:0c:f7
Nic2: 00:1a:4a:a8:0c:f1
Updated by Yama Kasi over 10 years ago
I just did another test with a new host:
I needed to change the networks on the nics again on the oVirt side and the installer started, it installs right but the finisch script is not runned because of the changed mac-address (I think).
Updated by Lukas Zapletal over 10 years ago
Yama-san,
is this realy problem of Foreman? I believe this is problem of the distribution you are installing. Modern distributions name interfaces in a way that they don't mess up. Or it can be problem of the OS installer as well. Give us more details in this regard here.
Updated by Yama Kasi over 10 years ago
Hi,
What we have found out is the following:
Foreman adds a VM and after it it adds the nics to it, this seems to be the problem.
The oVirt guys had this problem and fixed it by creating the right order on a VM create WITH Nics at once. Adding afterall can still cause this problem.
A solution, and the oVirt guys where not sure if they support that yet, would be to add the Nics through the API when the VM is created, so not after the creation.
I hope this helps.
Updated by Lukas Zapletal over 10 years ago
Hmmm that sounds like huge refactoring, isn't there any other solution?
Updated by Yama Kasi over 10 years ago
The oVirt guys where looking into it, Ohad Levi was not online so we couln't include him in the conversation.
Any ideas are welcome, but it seems to be that a refactor is needed and a workaround is looked at for now.
Updated by Moti Asayag over 10 years ago
Yama Kasi wrote:
Hi,
What we have found out is the following:
Foreman adds a VM and after it it adds the nics to it, this seems to be the problem.
The oVirt guys had this problem and fixed it by creating the right order on a VM create WITH Nics at once. Adding afterall can still cause this problem.
A solution, and the oVirt guys where not sure if they support that yet, would be to add the Nics through the API when the VM is created, so not after the creation.
That RFE is still open:
Bug 999969 - [RFE] Ability to add multiple NICs to VM on create VM
https://bugzilla.redhat.com/show_bug.cgi?id=999969
I hope this helps.
Updated by Anonymous over 7 years ago
- Status changed from New to Rejected
problem was on the ovirt side, BZ got fixed.