Re: [ovirt-users] Network Interface order changed after reboot

2016-06-27 Thread ovirt 

Hi Dan,

I'm using the kernal parameter net.ifnames=0 to have the old naming schema.

I will try to get rid of it on the machine and check if this is solving 
my issue.


Best regards

Christoph

Am 27.06.2016 um 08:29 schrieb Dan Kenigsberg:

On Sun, Jun 26, 2016 at 03:59:31PM +0300, Yedidyah Bar David wrote:

On Sun, Jun 26, 2016 at 3:51 PM, Edward Haas  wrote:


On Thu, Jun 23, 2016 at 3:49 PM,  wrote:

Hi List,

I have two nodes (running CentOS 7) and the network interface order
changed for some interfaces after every reboot.

The configurations are done through the oVirt GUI. So the ifcfg-ethX
scripts are configured automatically by VDSM.

Is there any option to get this configured to be stable?

Best regards and thank you

Christoph

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Hi Christoph,

VDSM indeed edits and takes ownership of the interfaces for the networks it
manages.
However, editing the ifcfg files should not change anything in the order of
the devices, unless it was originally set
in an unsupported fashion. An ifcfg file is bound to a specific device name
and I'm not familiar to device names
floating around randomly.
Perhaps you should elaborate more on what it means by 'order changed'.

Here is an example of a setup we do not support (pre adding the host to
Engine):
The initial ifcfg file name: ifcfg-eth0
The initial ifcfg file content: DEVICE="eth1"
In this configuration, the name of the ifcfg file is inconsistent with the
name of the device it represents.
VDSM expects them to me in sync.

Please provide the ifcfg files before and after you add the host to Engine.

Perhaps Christoph refers to the problem that [1] was meant to solve?

[1] 
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

To add on what didi says, this should be the default with el7's systemd.
It is surprising that your nics are named eth*, and not by the
predictable nic name scheme.

Maybe if you share your `lspci -vvv` and /var/log/messages of two
different boots, we can have a hint regarding your instability.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Dan Kenigsberg 
On Sun, Jun 26, 2016 at 03:59:31PM +0300, Yedidyah Bar David wrote:
> On Sun, Jun 26, 2016 at 3:51 PM, Edward Haas  wrote:
> >
> >
> > On Thu, Jun 23, 2016 at 3:49 PM,  wrote:
> >>
> >> Hi List,
> >>
> >> I have two nodes (running CentOS 7) and the network interface order
> >> changed for some interfaces after every reboot.
> >>
> >> The configurations are done through the oVirt GUI. So the ifcfg-ethX
> >> scripts are configured automatically by VDSM.
> >>
> >> Is there any option to get this configured to be stable?
> >>
> >> Best regards and thank you
> >>
> >> Christoph
> >>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >
> >
> > Hi Christoph,
> >
> > VDSM indeed edits and takes ownership of the interfaces for the networks it
> > manages.
> > However, editing the ifcfg files should not change anything in the order of
> > the devices, unless it was originally set
> > in an unsupported fashion. An ifcfg file is bound to a specific device name
> > and I'm not familiar to device names
> > floating around randomly.
> > Perhaps you should elaborate more on what it means by 'order changed'.
> >
> > Here is an example of a setup we do not support (pre adding the host to
> > Engine):
> > The initial ifcfg file name: ifcfg-eth0
> > The initial ifcfg file content: DEVICE="eth1"
> > In this configuration, the name of the ifcfg file is inconsistent with the
> > name of the device it represents.
> > VDSM expects them to me in sync.
> >
> > Please provide the ifcfg files before and after you add the host to Engine.
> 
> Perhaps Christoph refers to the problem that [1] was meant to solve?
> 
> [1] 
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

To add on what didi says, this should be the default with el7's systemd.
It is surprising that your nics are named eth*, and not by the
predictable nic name scheme.

Maybe if you share your `lspci -vvv` and /var/log/messages of two
different boots, we can have a hint regarding your instability.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread ovirt 
No I just eth0 was configured during OS installation. All other 
interface have been configured through the oVirt GUI.


Best regards
Christoph

Am 26.06.2016 um 16:08 schrieb Edward Haas:




On Sun, Jun 26, 2016 at 4:48 PM, > wrote:


Hi Edy,

please find some config files below. I did the interface config
only through the oVirt GUI.

I mean by reordering that after every reboot some interfaces are
not the same as before. That means I need to change the cables
after reboot.


This sounds like the problem Didi referenced to.

Before you configured the interfaces through oVirt, wasn't there any 
ifcfg files?
(just to understand why you have not seen this before, without vdsm on 
the host)



[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Generated by VDSM version 4.17.28-1.el7
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
MTU=1500
DEFROUTE=yes
NM_CONTROLLED=no
IPV6INIT=no
[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Generated by VDSM version 4.17.23-0.el7.centos
DEVICE=eth1
BRIDGE=Test-LAN-SW1
ONBOOT=yes
MTU=1500
NM_CONTROLLED=no
IPV6INIT=no
[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
# Generated by VDSM version 4.17.23-0.el7.centos
DEVICE=eth2
BRIDGE=PC-LAN
ONBOOT=yes
MTU=1500
NM_CONTROLLED=no
IPV6INIT=no

Best regards
Christoph


Am 26.06.2016 um 14:51 schrieb Edward Haas:



On Thu, Jun 23, 2016 at 3:49 PM, mailto:ov...@timmi.org>> wrote:

Hi List,

I have two nodes (running CentOS 7) and the network interface
order changed for some interfaces after every reboot.

The configurations are done through the oVirt GUI. So the
ifcfg-ethX scripts are configured automatically by VDSM.

Is there any option to get this configured to be stable?

Best regards and thank you

Christoph

___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users


Hi Christoph,

VDSM indeed edits and takes ownership of the interfaces for the
networks it manages.
However, editing the ifcfg files should not change anything in
the order of the devices, unless it was originally set
in an unsupported fashion. An ifcfg file is bound to a specific
device name and I'm not familiar to device names
floating around randomly.
Perhaps you should elaborate more on what it means by 'order
changed'.

Here is an example of a setup we do not support (pre adding the
host to Engine):
The initial ifcfg file name: ifcfg-eth0
The initial ifcfg file content: DEVICE="eth1"
In this configuration, the name of the ifcfg file is inconsistent
with the name of the device it represents.
VDSM expects them to me in sync.

Please provide the ifcfg files before and after you add the host
to Engine.

Thanks,
Edy.






___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Edward Haas 
On Sun, Jun 26, 2016 at 4:48 PM,  wrote:

> Hi Edy,
>
> please find some config files below. I did the interface config only
> through the oVirt GUI.
>
> I mean by reordering that after every reboot some interfaces are not the
> same as before. That means I need to change the cables after reboot.
>

This sounds like the problem Didi referenced to.

Before you configured the interfaces through oVirt, wasn't there any ifcfg
files?
(just to understand why you have not seen this before, without vdsm on the
host)


>
> [root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
> # Generated by VDSM version 4.17.28-1.el7
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=dhcp
> MTU=1500
> DEFROUTE=yes
> NM_CONTROLLED=no
> IPV6INIT=no
> [root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
> # Generated by VDSM version 4.17.23-0.el7.centos
> DEVICE=eth1
> BRIDGE=Test-LAN-SW1
> ONBOOT=yes
> MTU=1500
> NM_CONTROLLED=no
> IPV6INIT=no
> [root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
> # Generated by VDSM version 4.17.23-0.el7.centos
> DEVICE=eth2
> BRIDGE=PC-LAN
> ONBOOT=yes
> MTU=1500
> NM_CONTROLLED=no
> IPV6INIT=no
>
> Best regards
> Christoph
>
>
> Am 26.06.2016 um 14:51 schrieb Edward Haas:
>
>
>
> On Thu, Jun 23, 2016 at 3:49 PM,  wrote:
>
>> Hi List,
>>
>> I have two nodes (running CentOS 7) and the network interface order
>> changed for some interfaces after every reboot.
>>
>> The configurations are done through the oVirt GUI. So the ifcfg-ethX
>> scripts are configured automatically by VDSM.
>>
>> Is there any option to get this configured to be stable?
>>
>> Best regards and thank you
>>
>> Christoph
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
> Hi Christoph,
>
> VDSM indeed edits and takes ownership of the interfaces for the networks
> it manages.
> However, editing the ifcfg files should not change anything in the order
> of the devices, unless it was originally set
> in an unsupported fashion. An ifcfg file is bound to a specific device
> name and I'm not familiar to device names
> floating around randomly.
> Perhaps you should elaborate more on what it means by 'order changed'.
>
> Here is an example of a setup we do not support (pre adding the host to
> Engine):
> The initial ifcfg file name: ifcfg-eth0
> The initial ifcfg file content: DEVICE="eth1"
> In this configuration, the name of the ifcfg file is inconsistent with the
> name of the device it represents.
> VDSM expects them to me in sync.
>
> Please provide the ifcfg files before and after you add the host to Engine.
>
> Thanks,
> Edy.
>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread ovirt 

Hi Edy,

please find some config files below. I did the interface config only 
through the oVirt GUI.


I mean by reordering that after every reboot some interfaces are not the 
same as before. That means I need to change the cables after reboot.


[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
# Generated by VDSM version 4.17.28-1.el7
DEVICE=eth0
ONBOOT=yes
BOOTPROTO=dhcp
MTU=1500
DEFROUTE=yes
NM_CONTROLLED=no
IPV6INIT=no
[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Generated by VDSM version 4.17.23-0.el7.centos
DEVICE=eth1
BRIDGE=Test-LAN-SW1
ONBOOT=yes
MTU=1500
NM_CONTROLLED=no
IPV6INIT=no
[root@lxedna ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth2
# Generated by VDSM version 4.17.23-0.el7.centos
DEVICE=eth2
BRIDGE=PC-LAN
ONBOOT=yes
MTU=1500
NM_CONTROLLED=no
IPV6INIT=no

Best regards
Christoph

Am 26.06.2016 um 14:51 schrieb Edward Haas:



On Thu, Jun 23, 2016 at 3:49 PM, > wrote:


Hi List,

I have two nodes (running CentOS 7) and the network interface
order changed for some interfaces after every reboot.

The configurations are done through the oVirt GUI. So the
ifcfg-ethX scripts are configured automatically by VDSM.

Is there any option to get this configured to be stable?

Best regards and thank you

Christoph

___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users


Hi Christoph,

VDSM indeed edits and takes ownership of the interfaces for the 
networks it manages.
However, editing the ifcfg files should not change anything in the 
order of the devices, unless it was originally set
in an unsupported fashion. An ifcfg file is bound to a specific device 
name and I'm not familiar to device names

floating around randomly.
Perhaps you should elaborate more on what it means by 'order changed'.

Here is an example of a setup we do not support (pre adding the host 
to Engine):

The initial ifcfg file name: ifcfg-eth0
The initial ifcfg file content: DEVICE="eth1"
In this configuration, the name of the ifcfg file is inconsistent with 
the name of the device it represents.

VDSM expects them to me in sync.

Please provide the ifcfg files before and after you add the host to 
Engine.


Thanks,
Edy.



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread ovirt 

Hi,

I'm using currently the following:

But the problem is not new.

ovirt-engine.noarch   3.6.6.2-1.el7.centos @ovirt-3.6

vdsm.noarch   4.17.28-1.el7 @centos-ovirt36

Best regards

Christoph


Am 26.06.2016 um 14:19 schrieb Yevgeny Zaspitsky:

BTW, what oVirt (vdsm&engine) version do you use?

On Sun, Jun 26, 2016 at 3:15 PM, Yevgeny Zaspitsky 
mailto:yzasp...@redhat.com>> wrote:


Christoph,

Are those nodes bare-metal or they're VMs?

Regards,
Yevgeny

On Thu, Jun 23, 2016 at 3:49 PM, mailto:ov...@timmi.org>> wrote:

Hi List,

I have two nodes (running CentOS 7) and the network interface
order changed for some interfaces after every reboot.

The configurations are done through the oVirt GUI. So the
ifcfg-ethX scripts are configured automatically by VDSM.

Is there any option to get this configured to be stable?

Best regards and thank you

Christoph

___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users





___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread ovirt 

Hi Yevgeny,

this are real machines.

Best regards
Christoph

Am 26.06.2016 um 14:15 schrieb Yevgeny Zaspitsky:

Christoph,

Are those nodes bare-metal or they're VMs?

Regards,
Yevgeny

On Thu, Jun 23, 2016 at 3:49 PM, > wrote:


Hi List,

I have two nodes (running CentOS 7) and the network interface
order changed for some interfaces after every reboot.

The configurations are done through the oVirt GUI. So the
ifcfg-ethX scripts are configured automatically by VDSM.

Is there any option to get this configured to be stable?

Best regards and thank you

Christoph

___
Users mailing list
Users@ovirt.org 
http://lists.ovirt.org/mailman/listinfo/users




___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Yedidyah Bar David 
On Sun, Jun 26, 2016 at 3:51 PM, Edward Haas  wrote:
>
>
> On Thu, Jun 23, 2016 at 3:49 PM,  wrote:
>>
>> Hi List,
>>
>> I have two nodes (running CentOS 7) and the network interface order
>> changed for some interfaces after every reboot.
>>
>> The configurations are done through the oVirt GUI. So the ifcfg-ethX
>> scripts are configured automatically by VDSM.
>>
>> Is there any option to get this configured to be stable?
>>
>> Best regards and thank you
>>
>> Christoph
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>
>
> Hi Christoph,
>
> VDSM indeed edits and takes ownership of the interfaces for the networks it
> manages.
> However, editing the ifcfg files should not change anything in the order of
> the devices, unless it was originally set
> in an unsupported fashion. An ifcfg file is bound to a specific device name
> and I'm not familiar to device names
> floating around randomly.
> Perhaps you should elaborate more on what it means by 'order changed'.
>
> Here is an example of a setup we do not support (pre adding the host to
> Engine):
> The initial ifcfg file name: ifcfg-eth0
> The initial ifcfg file content: DEVICE="eth1"
> In this configuration, the name of the ifcfg file is inconsistent with the
> name of the device it represents.
> VDSM expects them to me in sync.
>
> Please provide the ifcfg files before and after you add the host to Engine.

Perhaps Christoph refers to the problem that [1] was meant to solve?

[1] 
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
-- 
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Edward Haas 
On Thu, Jun 23, 2016 at 3:49 PM,  wrote:

> Hi List,
>
> I have two nodes (running CentOS 7) and the network interface order
> changed for some interfaces after every reboot.
>
> The configurations are done through the oVirt GUI. So the ifcfg-ethX
> scripts are configured automatically by VDSM.
>
> Is there any option to get this configured to be stable?
>
> Best regards and thank you
>
> Christoph
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>

Hi Christoph,

VDSM indeed edits and takes ownership of the interfaces for the networks it
manages.
However, editing the ifcfg files should not change anything in the order of
the devices, unless it was originally set
in an unsupported fashion. An ifcfg file is bound to a specific device name
and I'm not familiar to device names
floating around randomly.
Perhaps you should elaborate more on what it means by 'order changed'.

Here is an example of a setup we do not support (pre adding the host to
Engine):
The initial ifcfg file name: ifcfg-eth0
The initial ifcfg file content: DEVICE="eth1"
In this configuration, the name of the ifcfg file is inconsistent with the
name of the device it represents.
VDSM expects them to me in sync.

Please provide the ifcfg files before and after you add the host to Engine.

Thanks,
Edy.
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Yevgeny Zaspitsky 
BTW, what oVirt (vdsm&engine) version do you use?

On Sun, Jun 26, 2016 at 3:15 PM, Yevgeny Zaspitsky 
wrote:

> Christoph,
>
> Are those nodes bare-metal or they're VMs?
>
> Regards,
> Yevgeny
>
> On Thu, Jun 23, 2016 at 3:49 PM,  wrote:
>
>> Hi List,
>>
>> I have two nodes (running CentOS 7) and the network interface order
>> changed for some interfaces after every reboot.
>>
>> The configurations are done through the oVirt GUI. So the ifcfg-ethX
>> scripts are configured automatically by VDSM.
>>
>> Is there any option to get this configured to be stable?
>>
>> Best regards and thank you
>>
>> Christoph
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Network Interface order changed after reboot

2016-06-26 Thread Yevgeny Zaspitsky 
Christoph,

Are those nodes bare-metal or they're VMs?

Regards,
Yevgeny

On Thu, Jun 23, 2016 at 3:49 PM,  wrote:

> Hi List,
>
> I have two nodes (running CentOS 7) and the network interface order
> changed for some interfaces after every reboot.
>
> The configurations are done through the oVirt GUI. So the ifcfg-ethX
> scripts are configured automatically by VDSM.
>
> Is there any option to get this configured to be stable?
>
> Best regards and thank you
>
> Christoph
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users