On Mon, May 11, 2015 at 10:25:36AM +0000, John Joseph wrote:
On Monday, 11 May 2015 2:14 PM, Yedidyah Bar David <didi@redhat.com> wrote: ----- Original Message -----
From: "John Joseph" <jjk_saji@yahoo.com> To: users@ovirt.org Sent: Sunday, May 10, 2015 2:37:39 PM Subject: [ovirt-users] My feedback on network setting after installing OVirt
Hi All,
Like to give my feedback about how the network interface behaved after OVirt I have used
CentOS 6.6 64 bit, updated
Ovirt stable from the repo
Now after the installation, and configuration you get "ovirtmgmt" interface and "ovirtmgmt" interface gets the IP address and everything is fine . Now reboot it
result is that when you give ifconfig , eth0 is not displayed and "ovirtmgmt" do not have IP address
This stage solved by giving ifconfig eth0 up
and restarting the network, it will give "ovirtmgmt" an IP now
So you have to do this on every reboot?
Yes on every reboot I have to do it
I tested it using different installation, with DHCP or manual configuration for eth0 , in both the case the same experience
Sounds a bit like [1]. Adding Petr, this bug's owner.
Can you please check/post relevant conf/log files (ifcfg*, vdsm/system logs etc)?
I don't think that the bug is related, as Joseph's case lacks any bond. Network should have been restored by Vdsm on its start up. However, in ovirt-3.5.0 there were cases where this has failed. Furthermore, we still have 1203422 vdsm should restore networks much earlier, to let net-dependent services start that is still on our TODO list. To understand precisely what happens on your host, we'd need your vdsm version, and as Didi asked - your {super,}vdsm.log and /var/log/message. However, to avoid the need of re-solving a solved bug, verify that you use vdsm-4.16.14 or later.