6:37 a.m.
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
I tested it using different installation, with DHCP or manual configuration for eth0 , in
both the case the same experience
Giving my feedback,
thanks
5:14 a.m.
----- Original Message -----
From: "John Joseph" <jjk_saji(a)yahoo.com>
To: users(a)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?
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)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1154399
Giving my feedback,
Thanks,
--
Didi
5:25 a.m.
On Monday, 11 May 2015 2:14 PM, Yedidyah Bar David <didi(a)redhat.com> wrote:
----- Original Message -----
From: "John Joseph" <jjk_saji(a)yahoo.com>
To: users(a)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)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1154399
Giving my feedback,
Thanks a Lot
Joseph John
Thanks,
--
Didi
6:08 a.m.
----- Original Message -----
From: "John Joseph" <jjk_saji(a)yahoo.com>
To: "Yedidyah Bar David" <didi(a)redhat.com>
Cc: users(a)ovirt.org, "Petr Horacek" <phoracek(a)redhat.com>
Sent: Monday, May 11, 2015 12:25:36 PM
Subject: Re: [ovirt-users] My feedback on network setting after installing OVirt
On Monday, 11 May 2015 2:14 PM, Yedidyah Bar David <didi(a)redhat.com> wrote:
----- Original Message -----
> From: "John Joseph" <jjk_saji(a)yahoo.com>
> To: users(a)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)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1154399
>
> Giving my feedback,
Thanks a Lot
Joseph John
Thanks,
--
Didi
Hello,
John, could you please compare your problem with the bug Didi mentioned
(but i don't think it's the same case, you don't use a manually created
bonding) and if it is not the case, create a new bug entry [2] and
provide us logs and exact steps to reproduce?
[2] https://bugzilla.redhat.com/enter_bug.cgi?product=oVirt
Thanks a lot and best regards,
Petr
12:41 p.m.
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(a)redhat.com> wrote:
----- Original Message -----
> From: "John Joseph" <jjk_saji(a)yahoo.com>
> To: users(a)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)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1154399
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.
4:12 a.m.
Hi All
Thanks for the support,
I had done a couple of installation after this to test, all of the installation which I
did later I choose minimum installation, when doing minimum installation I did not face
any interface problem, the machine boots up and the iterface is up
The issue was with the installation which I choose Desktop installation
Thanks
Joseph John
On Monday, 11 May 2015 9:41 PM, Dan Kenigsberg <danken(a)redhat.com> wrote:
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(a)redhat.com> wrote:
----- Original Message -----
> From: "John Joseph" <jjk_saji(a)yahoo.com>
> To: users(a)ovirt.org
> Sent: Sunday, May 10, 2015 2:37:39 PM
> Subject: [ovirt-users] My feedback on network setting after installing OVirt
>
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)?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1154399
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.
3506
days inactive
3514
days old
5 comments
4 participants
participants (4)
-
Dan Kenigsberg -
John Joseph -
Petr Horacek -
Yedidyah Bar David