Bug 1142909
| Summary: | NIC removed during initial configuration | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Piotr Kliczewski <pkliczew> | ||||||
| Component: | vdsm | Assignee: | Barak <bazulay> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Gil Klein <gklein> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 3.5 | CC: | bazulay, bugs, danken, ecohen, gklein, lsurette, mgoldboi, pkliczew, rbalakri, yeylon, ylavi | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | 3.6.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | network | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-08-26 09:24:13 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: |
|
||||||||
Created attachment 938520 [details]
vdms.log
Hey Piotr, how did you originally configure the eth0 device to get connectivity to it? Cause I see that we do setupnetworks for it without specifying a bootproto, hence losing the connectivity and attempting a rollback. When eth0 disappeared after the initial attempt I restored it by providing: DEVICE=eth0 HWADDR=52:54:00:38:b1:c0 ONBOOT=yes MTU=1500 BOOTPROTO=dhcp and it worked. I assume that the original dhclient configuration was manual or somehow not retrievable by vdsm. This happened when adding the host to the engine, right? If that's the case we should have reported to the engine that the connectivity was provided via dhcp anyway, and the setupNetworks should have successfully included bootproto='dhcp'. The other issue, and easier to find bug is: "why did the rollback not put dhclient back on eth0" It is possible that we have to special case removing the last ipaddress of a device that leaves the machine without a configured IP and just launch a dhclient on it. Please reopen when this is reproduced and the needed info is available. I have a vm with f20 which reproduces this issue every time. It seems that nic is removed during host deploy and network reconfiguration from NetworkManager to network service. Please let me know where to upload the img. Can you please check with latest 3.5.4? Or on 3.6.0? Sure, will check. I tested with 3.6 and it works. |
Created attachment 938519 [details] supervdsm.log Description of problem: During initial installation of vdsm on fresh centos 6 vm setupNetworks failed and eth0-network interface was removed after restore. How reproducible: Steps to Reproduce: 1. Run host install on fresh centos 6 vm 2. 3. Actual results: Missing nic/network communication not restored Expected results: network successfully configured Additional info: