On 24/01/14 08:31, Moti Asayag wrote:
----- Original Message -----
> From: "Federico Alberto Sayd" <fsayd(a)uncu.edu.ar>
> To: users(a)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(a)uncu.edu.ar>
>>> To: users(a)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(a)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.