Bug 1289210
| Summary: | oVirt Hosted Engine Appliance intermittently loses connectivity due to inability to restart network.service | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-appliance | Reporter: | Charlie Inglese <cinglese> | ||||
| Component: | Core | Assignee: | Fabian Deutsch <fdeutsch> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 3.6 | CC: | alukiano, bhughes, bugs, cinglese, fdeutsch, mavital | ||||
| Target Milestone: | ovirt-3.6.1 | Keywords: | Triaged | ||||
| Target Release: | 3.6 | Flags: | fdeutsch:
ovirt-3.6.z?
fdeutsch: ovirt-4.0.0? rule-engine: planning_ack? fdeutsch: devel_ack+ rule-engine: testing_ack+ |
||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | node | ||||||
| Fixed In Version: | oVirt-Engine-Appliance-CentOS-x86_64-7-20151211.ova | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-01-13 14:37:59 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
For clarification, the ens3 device appears in the ovirt-appliance kickstart, however, after a reboot the only network devices recognized by the VM are eth0 and lo. Thanks for the clarification. Do you ever see the ens3 NIC name inside the appliance, or do you only see it in the kickstart? Fabian, Yes, the ens3 NIC appears inside the appliance. ls /etc/sysconfig/network-scripts/ifcfg-*: ifcfg-ens3 ifcfg-eth0 ifcfg-lo ls /sys/class/net: eth0 lo cat /etc/sysconfig/network-scripts/ifcfg-ens3: # Generated by dracut initrd NAME="ens3" DEVICE="ens3" ONBOOT=yes NETBOOT=yes UUID="a5279ae3-6818-496a-a48e-4316785c905b" IPV6INIT=yes BOOTPROTO=dhcp TYPE=Ethernet Thanks for the report, for now I'm simply removing the configuration, but there should be a more structured approach to do this post-processing. Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected. Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected. Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone. Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. Will line 62 in https://gerrit.ovirt.org/#/c/50123/1/engine-appliance/data/ovirt-engine-appliance.ks.in also remove ifcfg-eth0? Yep, during build it will remove all ifcfg-e* files - there should just be one, which will then get removed. Please note: The file will be removed during the build. When the appliance is then booted up, NetworkManager and/or cloud-init should bring up the interface. I just checked an older appliance:
$ guestfish -ia ./images/22b78c06-116e-4b81-ad19-535dc649db3f/f1c319d5-393b-4b7d-b273-3bfff94f4112
Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.
Type: 'help' for help on commands
'man' to read the manual
'quit' to quit the shell
Operating system: CentOS Linux release 7.1.1503 (Core)
/dev/sda1 mounted on /
><fs> ls /etc/sysconfig/network-scripts/
ifcfg-ens3
ifcfg-lo
ifdown
…
This shows that ens3 is part of the image, but the in comment 3 shown eth0 is created during deployment.
Thus removing any ifcfg-e* file during the image build process, will only remove the ens3 file, not the eth0 file.
Hi Fabian, we not check centos appliance, I deployed hosted engine with rhevm-appliance-20151119.0-1.el7ev.noarch.rpm and it worked fine, if it enough for verification? Hey Artyom, please check the centos appliance separately because it is built in a slightly different way. Verified on oVirt-Engine-Appliance-CentOS-x86_64-7-20151216.ova, deploy succeed without any errors. oVirt 3.6.1 has been released, closing current release |
Created attachment 1103288 [details] ovirt hosted engine Description of problem: systemctl restart network fails due to incorrect /etc/sysconfig/network-scripts/ens3 file. Version-Release number of selected component (if applicable): ovirt-engine-appliance-20151104.0-1.el7.centos.noarch ovirt-engine-setup-3.6.0.3-1.el7.centos.noarch How reproducible: Frequently (has occurred on every oVirt 3.6 HEappliance deployment) Steps to Reproduce: 1. Install 3.6 ovirt appliance (using answer file) Actual results: Expected results: Additional info: If appears that the ens3 device is hard-coded into the KS for the appliance. Once the VM reboots, that device doesn't exist, which creates a failure condition for restarting the network service.