[Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)"
I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1.
This is my network config:
ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no
ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no
No others ifcfg-* files.
I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report....?
Thanks!
Federico
PD: Sorry for my basic english
I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up: http://www.ovirt.org/Bonding_VLAN_Bridge Hope this helps! -- Med Vänliga Hälsningar ------------------------------------------------------------------------------- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)"
Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log?
I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1.
This is my network config:
ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no
ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no
No others ifcfg-* files.
I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report....?
Thanks!
Federico
PD: Sorry for my basic english
I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up:
http://www.ovirt.org/Bonding_VLAN_Bridge
Hope this helps!
Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where "2" is the vlan id of your manamgement network), and from there on, do all configuration via Engine. I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure. One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default. Dan.
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)" Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host (same hardware), and it worked. The supervdsm.log whith the lines logged yesterday: http://pastebin.com/kpXrRd2w It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive. Thanks
I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1.
This is my network config:
ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no
ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no
No others ifcfg-* files.
I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report....?
Thanks!
Federico
PD: Sorry for my basic english
I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up:
http://www.ovirt.org/Bonding_VLAN_Bridge
Hope this helps! Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where "2" is the vlan id of your manamgement network), and from there on, do all configuration via Engine.
I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure.
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)" Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host (same hardware), and it worked.
The supervdsm.log whith the lines logged yesterday:
It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive.
I do not understand the error yet... I believe that in the text you have quoted, Engine complains that an interface has not joined a bond. But Engine's command to Vdsm MainProcess|Thread-15::DEBUG::2014-01-21 13:13:21,166::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'vlan': '70', 'ipaddr': '192.168.1.101', 'netmask': '255.255.255.0', 'STP': 'no', 'bridged': 'true'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120} contains no reference to a bond device, and seems to have succeeded. One notable problem is that the network definitions lack a 'gateway' parameter, which is very important for ovirtmgmt. Would you share your vdsm.log, too? The output of getCapabilities before and after setupNetworks may shed some light on the circumstances. Regads, Dan.
On 22/01/14 21:31, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)" Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host (same hardware), and it worked.
The supervdsm.log whith the lines logged yesterday:
It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive. I do not understand the error yet... I believe that in the text you have quoted, Engine complains that an interface has not joined a bond. But Engine's command to Vdsm
MainProcess|Thread-15::DEBUG::2014-01-21 13:13:21,166::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'vlan': '70', 'ipaddr': '192.168.1.101', 'netmask': '255.255.255.0', 'STP': 'no', 'bridged': 'true'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}
contains no reference to a bond device, and seems to have succeeded.
One notable problem is that the network definitions lack a 'gateway' parameter, which is very important for ovirtmgmt.
Would you share your vdsm.log, too? The output of getCapabilities before and after setupNetworks may shed some light on the circumstances.
Regads, Dan.
Exactly , Engine doesn't want to create the bond because the configuration of a nic have "unacceptable" parameters. But, specifically what parameters? Which interface? Could the error be more explicit? Engine complains about the contents of ifcfg-* or actual network config? or both? In any case I restarted network service after edit ifcfg-* files. I got the error when I tried to bond the interfaces. The ovirtmgmt was created by oVirt and bridged to eth0.70 when the host was installed via oVirt Engine. After, I tried to bond the two interfaces: eth0, (with ovirtmgmt attached to it) and eth1 (without config), then the gui showed the error about ifcfg-* parameters. I guess that the text that you quoted corresponds to the creation of ovirmgmnt network at install time. I don't find in supervdsm.log any references to the bond creation. vdsm.log: http://pastebin.com/AGSMBnkN Thanks
Hi Federico, ----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 4:56:22 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 22/01/14 21:31, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)" Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host (same hardware), and it worked.
The supervdsm.log whith the lines logged yesterday:
It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive. I do not understand the error yet... I believe that in the text you have quoted, Engine complains that an interface has not joined a bond. But Engine's command to Vdsm
MainProcess|Thread-15::DEBUG::2014-01-21 13:13:21,166::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'vlan': '70', 'ipaddr': '192.168.1.101', 'netmask': '255.255.255.0', 'STP': 'no', 'bridged': 'true'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}
contains no reference to a bond device, and seems to have succeeded.
One notable problem is that the network definitions lack a 'gateway' parameter, which is very important for ovirtmgmt.
Would you share your vdsm.log, too? The output of getCapabilities before and after setupNetworks may shed some light on the circumstances.
Regads, Dan.
Exactly , Engine doesn't want to create the bond because the configuration of a nic have "unacceptable" parameters.
But, specifically what parameters? Which interface? Could the error be more explicit?
Engine complains about the contents of ifcfg-* or actual network config? or both? In any case I restarted network service after edit ifcfg-* files.
I got the error when I tried to bond the interfaces. The ovirtmgmt was created by oVirt and bridged to eth0.70 when the host was installed via oVirt Engine. After, I tried to bond the two interfaces: eth0, (with ovirtmgmt attached to it) and eth1 (without config), then the gui showed the error about ifcfg-* parameters.
I guess that the text that you quoted corresponds to the creation of ovirmgmnt network at install time. I don't find in supervdsm.log any references to the bond creation.
vdsm.log: http://pastebin.com/AGSMBnkN
I took a closer look at the vdsm.log file and i've noticed that the 'getCapabilities' reports the following for the 'eth1' interface: nics': {'eth1': {'netmask': '', 'addr': '', 'hwaddr': 'e4:1f:13:1a:5b:da', 'cfg': {'UUID': '3d63cd78-57e5-4f26-81c4-8a342a342ef4', 'NM_CONTROLLED': 'yes', 'HWADDR': 'E4:1F:13:1A:5B:DA', 'BOOTPROTO': 'dhcp', 'DEVICE': 'eth1', 'TYPE': 'Ethernet', 'ONBOOT': 'no'}, 'ipv6addrs': ['fe80::e61f:13ff:fe1a:5bda/64'], 'speed': 1000, 'mtu': '1500'}, This in interface is configured with boot-protocol as 'dhcp' and cannot serve as a slave. In addition, it is marked as managed by the network manager which i'm not sure is advisable. This somehow defers from the output of the ifcfg-eth1 content which didn't specify any value for that device: ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes Adding to this file: NM_CONTROLLED=no BOOTPROTO=none and restarting the network service && vdsm would reflect this information to the engine which will allow to refer to such a nic as a slave when constructing a bond. The reason for not seeing any bond created in the [super]vdsm.log is due to the fact this action was blocked on the ovirt-engine side and never sent to vdsm. Regards, Moti
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 27/01/14 13:02, Moti Asayag wrote:
Hi Federico,
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 4:56:22 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 22/01/14 21:31, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote: > Hello: > > I am having problems with bonding > > I have installed Centos 6.5 in order to use it as host. I configured > eth0 with the vlan of the management network (Vlan 70). Then I > registered the host to the engine (3.3.2-1-el6) and the engine > installed oVirt in the host without problem. Ovirtmgmt was created > automatically and bridged with eth0.70. > > Now I need to bond a second network interface (eth1) with eth0. But > when I try to bond the nics, I get the next error: > > "A slave interface is not properly configured. Please verify slaves do > not contain any of the following properties: network name, boot > protocol, IP address, netmask, gateway or vlan-ID notation (as part of > interface's name or explicitly)" Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log? I get the error in the setup-network dialog in ovirt-engine.
Today I solved the issue copying the network config of other host (same hardware), and it worked.
The supervdsm.log whith the lines logged yesterday:
It would be nice if the error could be more explicit, i.e. telling the ifcfg-* that are conflictive. I do not understand the error yet... I believe that in the text you have quoted, Engine complains that an interface has not joined a bond. But Engine's command to Vdsm
MainProcess|Thread-15::DEBUG::2014-01-21 13:13:21,166::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call setupNetworks with ({'ovirtmgmt': {'nic': 'eth0', 'vlan': '70', 'ipaddr': '192.168.1.101', 'netmask': '255.255.255.0', 'STP': 'no', 'bridged': 'true'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}
contains no reference to a bond device, and seems to have succeeded.
One notable problem is that the network definitions lack a 'gateway' parameter, which is very important for ovirtmgmt.
Would you share your vdsm.log, too? The output of getCapabilities before and after setupNetworks may shed some light on the circumstances.
Regads, Dan.
Exactly , Engine doesn't want to create the bond because the configuration of a nic have "unacceptable" parameters.
But, specifically what parameters? Which interface? Could the error be more explicit?
Engine complains about the contents of ifcfg-* or actual network config? or both? In any case I restarted network service after edit ifcfg-* files.
I got the error when I tried to bond the interfaces. The ovirtmgmt was created by oVirt and bridged to eth0.70 when the host was installed via oVirt Engine. After, I tried to bond the two interfaces: eth0, (with ovirtmgmt attached to it) and eth1 (without config), then the gui showed the error about ifcfg-* parameters.
I guess that the text that you quoted corresponds to the creation of ovirmgmnt network at install time. I don't find in supervdsm.log any references to the bond creation.
vdsm.log: http://pastebin.com/AGSMBnkN
I took a closer look at the vdsm.log file and i've noticed that the 'getCapabilities' reports the following for the 'eth1' interface:
nics': {'eth1': {'netmask': '', 'addr': '', 'hwaddr': 'e4:1f:13:1a:5b:da', 'cfg': {'UUID': '3d63cd78-57e5-4f26-81c4-8a342a342ef4', 'NM_CONTROLLED': 'yes', 'HWADDR': 'E4:1F:13:1A:5B:DA', 'BOOTPROTO': 'dhcp', 'DEVICE': 'eth1', 'TYPE': 'Ethernet', 'ONBOOT': 'no'}, 'ipv6addrs': ['fe80::e61f:13ff:fe1a:5bda/64'], 'speed': 1000, 'mtu': '1500'},
This in interface is configured with boot-protocol as 'dhcp' and cannot serve as a slave. In addition, it is marked as managed by the network manager which i'm not sure is advisable.
This somehow defers from the output of the ifcfg-eth1 content which didn't specify any value for that device:
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
Adding to this file: NM_CONTROLLED=no BOOTPROTO=none
and restarting the network service && vdsm would reflect this information to the engine which will allow to refer to such a nic as a slave when constructing a bond.
The reason for not seeing any bond created in the [super]vdsm.log is due to the fact this action was blocked on the ovirt-engine side and never sent to vdsm.
Regards, Moti
Thanks _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
I restarted network service with the config from ifcfg-* that previously posted. But I didn't restart the vdsm service. Regards Federico
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote:
<snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied. The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2]. [1] http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/20/noarch/mom-0.3.2... [2] http://jenkins.ovirt.org/view/All/job/manual-build-tarball/174/label=centos6...
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
[1] http://resources.ovirt.org/releases/3.4.0_pre/rpm/Fedora/20/noarch/mom-0.3.2...
[2] http://jenkins.ovirt.org/view/All/job/manual-build-tarball/174/label=centos6...
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 23/01/14 23:02 +0200, Itamar Heim wrote:
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
Yes, because (up until now) the mom build system was not compatible with other oVirt projects. That was fixed this week [1] so now we can release proper RPMs into the oVirt repositories. Next I want to do a MOM version bump and synchronize the official Fedora packages with what we have in oVirt. Any opinion on whether we should adopt the current MOM master (build system rewrite) this late in the 3.4 release process? If so, I will work with Sandro to make sure that rc1 has it updated. Othewise, we can do that for 3.4.1.
Il 23/01/2014 22:23, Adam Litke ha scritto:
On 23/01/14 23:02 +0200, Itamar Heim wrote:
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
Yes, because (up until now) the mom build system was not compatible with other oVirt projects. That was fixed this week [1] so now we can release proper RPMs into the oVirt repositories. Next I want to do a MOM version bump and synchronize the official Fedora packages with what we have in oVirt.
Any opinion on whether we should adopt the current MOM master (build system rewrite) this late in the 3.4 release process? If so, I will work with Sandro to make sure that rc1 has it updated. Othewise, we can do that for 3.4.1.
3.4.0 beta1 has mom-0.3.2-20140120.gitfd877c5.fc19.noarch.rpm built by jenkins http://jenkins.ovirt.org/view/Packaging/job/mom_create-rpms/35/ new build system is fine for me, I don't see any technical reason for not including current MOM master in 3.4.0 RC.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On Thu, Jan 23, 2014 at 04:23:48PM -0500, Adam Litke wrote:
On 23/01/14 23:02 +0200, Itamar Heim wrote:
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote:
On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
The supervdsm.log whith the lines logged yesterday:
On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
Yes, because (up until now) the mom build system was not compatible with other oVirt projects. That was fixed this week [1] so now we can release proper RPMs into the oVirt repositories. Next I want to do a MOM version bump and synchronize the official Fedora packages with what we have in oVirt.
Any opinion on whether we should adopt the current MOM master (build system rewrite) this late in the 3.4 release process? If so, I will work with Sandro to make sure that rc1 has it updated. Othewise, we can do that for 3.4.1.
Currently 3.4 beta includes http://resources.ovirt.org/releases/beta/rpm/EL/6/noarch/mom-0.3.2-3.el6.noa... which is sorely outdated, as you say. We should fix this as soon as possible. Branching one week too late is a small price to pay, imo.
Hi, what about older but still supported ovirt version? I ask for all the 3.3.x people, we could need the bugfixes from mom, too. Am 24.01.2014 11:44, schrieb Dan Kenigsberg:
On Thu, Jan 23, 2014 at 04:23:48PM -0500, Adam Litke wrote:
On 23/01/14 23:02 +0200, Itamar Heim wrote:
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote: > On 22/01/14 12:13, Dan Kenigsberg wrote: <snip>
> The supervdsm.log whith the lines logged yesterday: > > http://pastebin.com/kpXrRd2w > On an unrelated matter: this log includes
MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call ksmTune with ({},) {} MainProcess|PolicyEngine::DEBUG::2014-01-21 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) return ksmTune with None
spam every 10 seconds. Federico, which version of mom do you have installed? I thought we have solved a similar issue in the past.
mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
Yes, because (up until now) the mom build system was not compatible with other oVirt projects. That was fixed this week [1] so now we can release proper RPMs into the oVirt repositories. Next I want to do a MOM version bump and synchronize the official Fedora packages with what we have in oVirt.
Any opinion on whether we should adopt the current MOM master (build system rewrite) this late in the 3.4 release process? If so, I will work with Sandro to make sure that rc1 has it updated. Othewise, we can do that for 3.4.1.
Currently 3.4 beta includes http://resources.ovirt.org/releases/beta/rpm/EL/6/noarch/mom-0.3.2-3.el6.noa... which is sorely outdated, as you say. We should fix this as soon as possible. Branching one week too late is a small price to pay, imo. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
-- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
On 01/27/2014 04:39 PM, Sven Kieske wrote:
Hi,
what about older but still supported ovirt version? I ask for all the 3.3.x people, we could need the bugfixes from mom, too.
the host side packages are all supposed to be backward compatible, so once this is fixed for latets vdsm/mom/etc., you should be able to use this with ovirt 3.2 engine as well, etc.?
Am 24.01.2014 11:44, schrieb Dan Kenigsberg:
On Thu, Jan 23, 2014 at 04:23:48PM -0500, Adam Litke wrote:
On 23/01/14 23:02 +0200, Itamar Heim wrote:
On 01/23/2014 08:04 PM, Adam Litke wrote:
On 23/01/14 10:43 -0300, Federico Alberto Sayd wrote:
On 22/01/14 21:32, Dan Kenigsberg wrote: > On Wed, Jan 22, 2014 at 01:57:35PM -0300, Federico Alberto Sayd wrote: >> On 22/01/14 12:13, Dan Kenigsberg wrote: > <snip> > >> The supervdsm.log whith the lines logged yesterday: >> >> http://pastebin.com/kpXrRd2w >> > On an unrelated matter: this log includes > > MainProcess|PolicyEngine::DEBUG::2014-01-21 > 13:13:41,187::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call > ksmTune with ({},) {} > MainProcess|PolicyEngine::DEBUG::2014-01-21 > 13:13:41,188::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) > return ksmTune with None > MainProcess|PolicyEngine::DEBUG::2014-01-21 > 13:13:51,220::supervdsmServer::95::SuperVdsm.ServerCallback::(wrapper) call > ksmTune with ({},) {} > MainProcess|PolicyEngine::DEBUG::2014-01-21 > 13:13:51,220::supervdsmServer::102::SuperVdsm.ServerCallback::(wrapper) > return ksmTune with None > > spam every 10 seconds. Federico, which version of mom do you have > installed? I > thought we have solved a similar issue in the past. > > mom-0.3.2-6.el6.noarch
This is the upstream version of mom which (sadly) is far too old and is missing a bunch of features. For Fedora, we are building master and releasing versions like mom-0.3.2-20140120.gitfd877c5.fc20 [1] which have lots of ovirt-specific fixes applied.
The fix is to have someone rebuild the mom RPM for el6 since the last refresh happened on August 13 (!). For now, please try to upgrade to this build of master [2].
any reason we don't build it via jenkins to resources.ovirt.org like other rpms?
Yes, because (up until now) the mom build system was not compatible with other oVirt projects. That was fixed this week [1] so now we can release proper RPMs into the oVirt repositories. Next I want to do a MOM version bump and synchronize the official Fedora packages with what we have in oVirt.
Any opinion on whether we should adopt the current MOM master (build system rewrite) this late in the 3.4 release process? If so, I will work with Sandro to make sure that rc1 has it updated. Othewise, we can do that for 3.4.1.
Currently 3.4 beta includes http://resources.ovirt.org/releases/beta/rpm/EL/6/noarch/mom-0.3.2-3.el6.noa... which is sorely outdated, as you say. We should fix this as soon as possible. Branching one week too late is a small price to pay, imo. _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Wed, 2014-01-22 at 15:13 +0000, Dan Kenigsberg wrote:
On Wed, Jan 22, 2014 at 07:43:52AM +0000, Karli Sjöberg wrote:
On Tue, 2014-01-21 at 21:22 -0300, Federico Sayd wrote:
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)"
Federico, where exactly do you get this error? Would you attach the setupNetwork log from supervdsmd.log?
I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1.
This is my network config:
ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no
ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no
No others ifcfg-* files.
I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report....?
Thanks!
Federico
PD: Sorry for my basic english
I´ve seen issues from folks trying to configure Host network through webadmin and failing one too many times now, so I decided to write something up:
http://www.ovirt.org/Bonding_VLAN_Bridge
Hope this helps!
Thanks Karli! Though it SHOULD be possible to start with eth0 and eth0.2 on the host (where "2" is the vlan id of your manamgement network), and from there on, do all configuration via Engine.
I'd like to automate as much as possible out of this process, and iron out remaining bugs. Hence, I would like to hear more about Federico's mode of failure.
Couldn´t agree with you more. But it´s always good to have something to fall back on, if only as reference, I think.
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
Does that imply that default gateway is supposed to be on the same net as ovirtmgmt? -- Med Vänliga Hälsningar ------------------------------------------------------------------------------- Karli Sjöberg Swedish University of Agricultural Sciences Box 7079 (Visiting Address Kronåsvägen 8) S-750 07 Uppsala, Sweden Phone: +46-(0)18-67 15 66 karli.sjoberg@slu.se _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Thu, Jan 23, 2014 at 06:50:59AM +0000, Karli Sjöberg wrote:
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
Does that imply that default gateway is supposed to be on the same net as ovirtmgmt?
Yes, and that's what happening whenever you make changes to ovirtmgmt via Vdsm.
On Thu, 2014-01-23 at 09:34 +0000, Dan Kenigsberg wrote:
On Thu, Jan 23, 2014 at 06:50:59AM +0000, Karli Sjöberg wrote:
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
Does that imply that default gateway is supposed to be on the same net as ovirtmgmt?
Yes, and that's what happening whenever you make changes to ovirtmgmt via Vdsm.
To tell you the truth, that makes me rather uncomfortable since we have set up our ovirtmgmt on a non-routed, "black" net, only used for _mgmt_ (thought that was the point). The display network is set up on a another logcal network, a routed net, which is where we also have the default gateway. Is this now a "wrong/bad" way to go about it? /K
From 3.3, you can define gateways on the other networks. These will be used via
Hi Karli, Normally we configure the host's default gateway on the ovirtmgmt network. If your engine is in the same subnet as all of your hosts, then it's not to define a getway on the ovirtmgmt network. source routing. For example, if you set a gateway on the display network, but leave the gateway blank for the ovirtmgmt network, then you'll see that 'ip route' won't list a default gateway. However, we configure source routing so that all traffic coming in to the display network on the host, will be returned via that network's gateway. You can view source routing rules via: ip rule Then ip route show table %s, for each table listed in ip rule. Assaf Muller, Cloud Networking Engineer Red Hat ----- Original Message ----- From: "Karli Sjöberg" <Karli.Sjoberg@slu.se> To: danken@redhat.com Cc: amuller@redhat.com, fsayd@uncu.edu.ar, users@ovirt.org Sent: Thursday, January 23, 2014 12:00:52 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured" On Thu, 2014-01-23 at 09:34 +0000, Dan Kenigsberg wrote:
On Thu, Jan 23, 2014 at 06:50:59AM +0000, Karli Sjöberg wrote:
One comment to your wiki page: in order to better intergrate with our recent source-routing support (mostly useful for display network), please set GATEWAY only in ifcfg-ovirtmgmt, and remember to set DEFROUTE=no in any other ifcfg that mentions IPADDR so as not to override the default.
Dan.
Does that imply that default gateway is supposed to be on the same net as ovirtmgmt?
Yes, and that's what happening whenever you make changes to ovirtmgmt via Vdsm.
To tell you the truth, that makes me rather uncomfortable since we have set up our ovirtmgmt on a non-routed, "black" net, only used for _mgmt_ (thought that was the point). The display network is set up on a another logcal network, a routed net, which is where we also have the default gateway. Is this now a "wrong/bad" way to go about it? /K
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
"A slave interface is not properly configured. Please verify slaves do not contain any of the following properties: network name, boot protocol, IP address, netmask, gateway or vlan-ID notation (as part of interface's name or explicitly)"
I delete any unnecessary parameters from ifcfg-eth0 and ifcfg-eth1.
This is my network config:
ifcfg-eth0: DEVICE=eth0 TYPE=Ethernet ONBOOT=yes
ifcfg-eth1: DEVIC E=eth1 TYPE=Ethernet ONBOOT=yes
ifcfg-eth0.70: # Generated by VDSM version 4.13.2-1.el6 DEVICE=eth0.70 ONBOOT=yes VLAN=yes BRIDGE=ovirtmgmt NM_CONTROLLED=no STP=no
ifcfg-ovirtmgmt: # Generated by VDSM version 4.13.2-1.el6 DEVICE=ovirtmgmt ONBOOT=yes TYPE=Bridge DELAY=0 IPADDR=192.168.1.101 NETMASK=255.255.255.0 BOOTPROTO=none DEFROUTE=yes NM_CONTROLLED=no STP=no
No others ifcfg-* files.
I don't see the parameters that oVirt doesn't like. Any clue, workaround, bug report....?
Thanks!
Federico
PD: Sorry for my basic english
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 23/01/14 07:02, Moti Asayag wrote:
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
Via webadmin Setup Network (Web GUI)
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 3:57:53 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 23/01/14 07:02, Moti Asayag wrote:
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
Via webadmin Setup Network (Web GUI)
Does the setup dialog presents the new configuration when you create the bond ? Meaning, does it draw the following ? eth0 -- |--bond0 --- ovirtmgmt (vlan 70) eth1 -- If it does, this is simply bug in the UI which should have better construct the parameters to the setup networks. Could you open a bug for it ? You may use the setup networks api (via rest-client or using the sdk) to specify the target configuration.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 24/01/14 08:31, Moti Asayag wrote:
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 3:57:53 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 23/01/14 07:02, Moti Asayag wrote:
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
Via webadmin Setup Network (Web GUI) Does the setup dialog presents the new configuration when you create the bond ? Meaning, does it draw the following ? eth0 -- |--bond0 --- ovirtmgmt (vlan 70) eth1 --
If it does, this is simply bug in the UI which should have better construct the parameters to the setup networks.
Could you open a bug for it ?
You may use the setup networks api (via rest-client or using the sdk) to specify the target configuration.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
No, the bond is never displayed in the web UI, the error prevents the bond creation. I already solved the problem, only I think that would be fine if the UI error be more explicit and include info about to the interface or interfaces with problematic configurations. I don't know if supervdsm.log or vdsm.log make reference to the interfaces that have unacceptable configurations.
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Friday, January 24, 2014 4:06:11 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 24/01/14 08:31, Moti Asayag wrote:
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 3:57:53 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 23/01/14 07:02, Moti Asayag wrote:
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
Via webadmin Setup Network (Web GUI) Does the setup dialog presents the new configuration when you create the bond ? Meaning, does it draw the following ? eth0 -- |--bond0 --- ovirtmgmt (vlan 70) eth1 --
If it does, this is simply bug in the UI which should have better construct the parameters to the setup networks.
Could you open a bug for it ?
You may use the setup networks api (via rest-client or using the sdk) to specify the target configuration.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
No, the bond is never displayed in the web UI, the error prevents the bond creation. I already solved the problem, only I think that would be fine if the UI error be more explicit and include info about to the interface or interfaces with problematic configurations.
I don't know if supervdsm.log or vdsm.log make reference to the interfaces that have unacceptable configurations.
The error indicates that the parameters sent from the UI to that engine weren't constructed properly. In this case the engine failed the action and it never reached the host. Lior, could you verify this scenario and see which fields left with improper values on the UI side ? _____________________________________________
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On 25/01/14 01:24, Moti Asayag wrote:
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Friday, January 24, 2014 4:06:11 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 24/01/14 08:31, Moti Asayag wrote:
----- Original Message -----
From: "Federico Alberto Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Thursday, January 23, 2014 3:57:53 PM Subject: Re: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
On 23/01/14 07:02, Moti Asayag wrote:
----- Original Message -----
From: "Federico Sayd" <fsayd@uncu.edu.ar> To: users@ovirt.org Sent: Wednesday, January 22, 2014 2:22:01 AM Subject: [Users] Centos 6.5 and bonding: "A slave interface is not properly configured"
Hello:
I am having problems with bonding
I have installed Centos 6.5 in order to use it as host. I configured eth0 with the vlan of the management network (Vlan 70). Then I registered the host to the engine (3.3.2-1-el6) and the engine installed oVirt in the host without problem. Ovirtmgmt was created automatically and bridged with eth0.70.
Now I need to bond a second network interface (eth1) with eth0. But when I try to bond the nics, I get the next error:
Could you describe how you've created the bond ? via webadmin setup networks dialog or via api ?
Via webadmin Setup Network (Web GUI) Does the setup dialog presents the new configuration when you create the bond ? Meaning, does it draw the following ? eth0 -- |--bond0 --- ovirtmgmt (vlan 70) eth1 --
If it does, this is simply bug in the UI which should have better construct the parameters to the setup networks.
Could you open a bug for it ?
You may use the setup networks api (via rest-client or using the sdk) to specify the target configuration.
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
No, the bond is never displayed in the web UI, the error prevents the bond creation. I already solved the problem, only I think that would be fine if the UI error be more explicit and include info about to the interface or interfaces with problematic configurations.
I don't know if supervdsm.log or vdsm.log make reference to the interfaces that have unacceptable configurations.
The error indicates that the parameters sent from the UI to that engine weren't constructed properly. In this case the engine failed the action and it never reached the host.
Lior, could you verify this scenario and see which fields left with improper values on the UI side ?
Apologies for the delay in responding. I tried running a similar scenario via the GUI on my deployment and it worked fine (and this part of the code shouldn't have changed recently). So I suspect the problem isn't with the Setup Networks GUI.
_____________________________________________
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
participants (11)
-
Adam Litke -
Assaf Muller -
Dan Kenigsberg -
Federico Alberto Sayd -
Federico Sayd
-
Itamar Heim -
Karli Sjöberg -
Lior Vernia -
Moti Asayag -
Sandro Bonazzola -
Sven Kieske