Bug 1568822
Summary: | can't configure network on VM | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] vdsm | Reporter: | Lucie Leistnerova <lleistne> | ||||
Component: | General | Assignee: | Dan Kenigsberg <danken> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Meni Yakove <myakove> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 4.20.0 | CC: | bugs, fromani, lleistne, michal.skrivanek | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-04-23 12:33:24 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Lucie Leistnerova
2018-04-18 09:45:16 UTC
Created attachment 1423421 [details]
console output
Sorry, I do not understand what you are attempting to do, nor do I notice any difference between the <interface> xml items. Are you able to boot from pxe at all? Can you describe it face-2-face to Michal, who might understand you better? the difference is in <link state="up"/> I'm trying to boot from PXE and I can't. VM's network interface is up and plugged. Starting it on newest 4.2.3 host failed to set up network and PXE is not loaded. On other hand starting the same VM on older 4.2 host works fine and I can boot from PXE. Francesco, might this be related to your recent vdsm-side cleanup? Shouldn't <link state="up"/> be sent by Engine? (In reply to Meni Yakove from comment #6) > Francesco, might this be related to your recent vdsm-side cleanup? > Shouldn't <link state="up"/> be sent by Engine? it is sent the same for both cases. Just on olde vdsm it's replaced entirely. However the problem is reported on the new host - so it's probably on the vdsm side or something with the host network configuration The newest host was upgraded from the same version as the older host is (4.20.23-1.el7ev.x86_64 -> 4.20.25-1.el7ev.x86_64). I'm not aware of doing some changes in the host's settings. After detailed Michal's investigation it seems, that the testing host's environment is broken and network is misconfigured. After upgrading second host, the VMs booted on it from PXE with success. So I'll close this issue. Feel free to reopen when the problem appears again. |