[ovirt-users] Re: problem with custom bond options

2020-07-27 Thread Jiří Sléžka
On 7/24/20 5:23 PM, Strahil Nikolov wrote:
> Hi Jiri,
> 
> you are the second person who mentions it.  Can you open a bug at 
> bugzilla.redhat.com  about that  ?

sure, here it is

https://bugzilla.redhat.com/show_bug.cgi?id=1860843

Best Regards,

Jiri Slezka


> 
> Best Regards,
> Strahil Nikolov
> 
> На 24 юли 2020 г. 16:30:02 GMT+03:00, "Jiří Sléžka"  
> написа:
>> On 7/24/20 11:36 AM, Jiří Sléžka wrote:
>>> On 7/24/20 10:56 AM, Ales Musil wrote:


 On Fri, Jul 24, 2020 at 10:40 AM Jiří Sléžka >>> > wrote:

 On 7/23/20 2:07 PM, Jiří Sléžka wrote:
 > On 7/23/20 12:35 PM, Ales Musil wrote:
 >>
 >>
 >> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka
>> >>> 
 >> >>
>> wrote:
 >>
 >>     On 7/23/20 11:03 AM, Ales Musil wrote:
 >>     >
 >>     >
 >>     > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka
 mailto:jiri.sle...@slu.cz>
 >>     >
 >>     > 
 >     >
 >>     >     Hi,
 >>     >
 >>     >     On 7/23/20 8:38 AM, Ales Musil wrote:
 >>     >     >
 >>     >     >
 >>     >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
 >>     mailto:jiri.sle...@slu.cz>
 >
 >>     >     > 
 >>
 >>     >     >  >
 >>     
 
>> wrote:
 >>     >     >
 >>     >     >     Hello,
 >>     >     >
 >>     >     >
 >>     >     > Hi,
 >>     >     >
 >>     >     >
 >>     >     >     CentOS8, oVirt 4.4.1.10-1.el8
 >>     >     >
 >>     >     >     I am trying to setup active-backup (mode=1)
 bonding mode
 >>     with
 >>     >     custom
 >>     >     >     properties. I have one 10GE switch, the
>> second is
 just 1G.
 >>     >     10GE link is
 >>     >     >     the primary one.
 >>     >     >
 >>     >     >     cat
>> /etc/sysconfig/network-scripts/ifcfg-bond0
 >>     >     >
 >>     >     >
 >>     >     > first of all in oVirt 4.4 the network-scripts are
>> not
 relevant
 >>     >     anymore.
 >>     >     > More relevant is output from 'nmstatectl show'.
 >>     >
 >>     >     thanks, I believed that ifcfg files still describes
>> saved
 >>     interface
 >>     >     configuration (even on nm managed interfaces)...
 >>     >
 >>     >
 >>     > It does but it might not be that detailed as we would
>> have
 hoped for.
 >>     > Another reason why I said that it is not relevant is of
 course if
 >>     > someone tries
 >>     > reconfigure the interface through network-scripts.
 >>
 >>     well, honestly I did that (modified ifcfg and then use
>> nmcli con
 >>     reload). So right way is using nmcli con modify command?
 >>
 >>
 >> Yes or nmstate. Just be aware that anything that you do to
>> interface
 >> outside of oVirt can have harmful impacts on the host and
>> overall
 oVirt
 >> state.
 >>  
 >>
 >>
 >>     >     from nmstatectl show I can see that bond0 has
>> specified mac
 >>     address
 >>     >
 >>     >   
 >>   

>>   
>> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
 >>     >
 >>     >     >     BONDING_OPTS="active_slave=ens5 downdelay=0
 miimon=100
 >>     >     >     mode=active-backup primary=ens5 updelay=0"
 >>     >     >     TYPE=Bond
 >>     >     >     BONDING_MASTER=yes
 >>     >     >     PROXY_METHOD=none
 >>     >     >     BROWSER_ONLY=no
 >>     >     >     IPV4_FAILURE_FATAL=no
 >>     >     >     IPV6_DISABLED=yes
 >>     >     >     IPV6INIT=no
 >>     >     >     NAME=bond0
 >>     >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
 >>     >     >     DEVICE=bond0
 >>     >     >     ONBOOT=yes
 >>     >     >     MTU=9000
 >>     >     >
 >>     >    

[ovirt-users] Re: problem with custom bond options

2020-07-24 Thread Strahil Nikolov via Users
Hi Jiri,

you are the second person who mentions it.  Can you open a bug at 
bugzilla.redhat.com  about that  ?

Best Regards,
Strahil Nikolov

На 24 юли 2020 г. 16:30:02 GMT+03:00, "Jiří Sléžka"  написа:
>On 7/24/20 11:36 AM, Jiří Sléžka wrote:
>> On 7/24/20 10:56 AM, Ales Musil wrote:
>>>
>>>
>>> On Fri, Jul 24, 2020 at 10:40 AM Jiří Sléžka >> > wrote:
>>>
>>> On 7/23/20 2:07 PM, Jiří Sléžka wrote:
>>> > On 7/23/20 12:35 PM, Ales Musil wrote:
>>> >>
>>> >>
>>> >> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka
>>> 
>>> >> >>
>wrote:
>>> >>
>>> >>     On 7/23/20 11:03 AM, Ales Musil wrote:
>>> >>     >
>>> >>     >
>>> >>     > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka
>>> mailto:jiri.sle...@slu.cz>
>>> >>     >
>>> >>     > 
>>> >> >>     >
>>> >>     >     Hi,
>>> >>     >
>>> >>     >     On 7/23/20 8:38 AM, Ales Musil wrote:
>>> >>     >     >
>>> >>     >     >
>>> >>     >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
>>> >>     mailto:jiri.sle...@slu.cz>
>>> >
>>> >>     >     
>>> >>
>>> >>     >     > >>  >> >
>>> >>     
>>> 
>wrote:
>>> >>     >     >
>>> >>     >     >     Hello,
>>> >>     >     >
>>> >>     >     >
>>> >>     >     > Hi,
>>> >>     >     >
>>> >>     >     >
>>> >>     >     >     CentOS8, oVirt 4.4.1.10-1.el8
>>> >>     >     >
>>> >>     >     >     I am trying to setup active-backup (mode=1)
>>> bonding mode
>>> >>     with
>>> >>     >     custom
>>> >>     >     >     properties. I have one 10GE switch, the
>second is
>>> just 1G.
>>> >>     >     10GE link is
>>> >>     >     >     the primary one.
>>> >>     >     >
>>> >>     >     >     cat
>/etc/sysconfig/network-scripts/ifcfg-bond0
>>> >>     >     >
>>> >>     >     >
>>> >>     >     > first of all in oVirt 4.4 the network-scripts are
>not
>>> relevant
>>> >>     >     anymore.
>>> >>     >     > More relevant is output from 'nmstatectl show'.
>>> >>     >
>>> >>     >     thanks, I believed that ifcfg files still describes
>saved
>>> >>     interface
>>> >>     >     configuration (even on nm managed interfaces)...
>>> >>     >
>>> >>     >
>>> >>     > It does but it might not be that detailed as we would
>have
>>> hoped for.
>>> >>     > Another reason why I said that it is not relevant is of
>>> course if
>>> >>     > someone tries
>>> >>     > reconfigure the interface through network-scripts.
>>> >>
>>> >>     well, honestly I did that (modified ifcfg and then use
>nmcli con
>>> >>     reload). So right way is using nmcli con modify command?
>>> >>
>>> >>
>>> >> Yes or nmstate. Just be aware that anything that you do to
>interface
>>> >> outside of oVirt can have harmful impacts on the host and
>overall
>>> oVirt
>>> >> state.
>>> >>  
>>> >>
>>> >>
>>> >>     >     from nmstatectl show I can see that bond0 has
>specified mac
>>> >>     address
>>> >>     >
>>> >>     >   
>>> >>   
>>>
>  
>https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
>>> >>     >
>>> >>     >     >     BONDING_OPTS="active_slave=ens5 downdelay=0
>>> miimon=100
>>> >>     >     >     mode=active-backup primary=ens5 updelay=0"
>>> >>     >     >     TYPE=Bond
>>> >>     >     >     BONDING_MASTER=yes
>>> >>     >     >     PROXY_METHOD=none
>>> >>     >     >     BROWSER_ONLY=no
>>> >>     >     >     IPV4_FAILURE_FATAL=no
>>> >>     >     >     IPV6_DISABLED=yes
>>> >>     >     >     IPV6INIT=no
>>> >>     >     >     NAME=bond0
>>> >>     >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
>>> >>     >     >     DEVICE=bond0
>>> >>     >     >     ONBOOT=yes
>>> >>     >     >     MTU=9000
>>> >>     >     >
>>> >>     >     >     When I try to add a custom parameter
>>> "fail_over_mac=active"
>>> >>     >     (which I
>>> >>     >     >     believe could solve my problems with stalled
>mac
>>> >>     addresses in
>>> >>     >     switch's
>>> >>     >     >     cam table in case of failover) I got...

[ovirt-users] Re: problem with custom bond options

2020-07-24 Thread Jiří Sléžka
On 7/24/20 11:36 AM, Jiří Sléžka wrote:
> On 7/24/20 10:56 AM, Ales Musil wrote:
>>
>>
>> On Fri, Jul 24, 2020 at 10:40 AM Jiří Sléžka > > wrote:
>>
>> On 7/23/20 2:07 PM, Jiří Sléžka wrote:
>> > On 7/23/20 12:35 PM, Ales Musil wrote:
>> >>
>> >>
>> >> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka > 
>> >> >> wrote:
>> >>
>> >>     On 7/23/20 11:03 AM, Ales Musil wrote:
>> >>     >
>> >>     >
>> >>     > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka
>> mailto:jiri.sle...@slu.cz>
>> >>     >
>> >>     > 
>> > >>     >
>> >>     >     Hi,
>> >>     >
>> >>     >     On 7/23/20 8:38 AM, Ales Musil wrote:
>> >>     >     >
>> >>     >     >
>> >>     >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
>> >>     mailto:jiri.sle...@slu.cz>
>> >
>> >>     >     
>> >>
>> >>     >     > >  > >
>> >>     
>>  wrote:
>> >>     >     >
>> >>     >     >     Hello,
>> >>     >     >
>> >>     >     >
>> >>     >     > Hi,
>> >>     >     >
>> >>     >     >
>> >>     >     >     CentOS8, oVirt 4.4.1.10-1.el8
>> >>     >     >
>> >>     >     >     I am trying to setup active-backup (mode=1)
>> bonding mode
>> >>     with
>> >>     >     custom
>> >>     >     >     properties. I have one 10GE switch, the second is
>> just 1G.
>> >>     >     10GE link is
>> >>     >     >     the primary one.
>> >>     >     >
>> >>     >     >     cat /etc/sysconfig/network-scripts/ifcfg-bond0
>> >>     >     >
>> >>     >     >
>> >>     >     > first of all in oVirt 4.4 the network-scripts are not
>> relevant
>> >>     >     anymore.
>> >>     >     > More relevant is output from 'nmstatectl show'.
>> >>     >
>> >>     >     thanks, I believed that ifcfg files still describes saved
>> >>     interface
>> >>     >     configuration (even on nm managed interfaces)...
>> >>     >
>> >>     >
>> >>     > It does but it might not be that detailed as we would have
>> hoped for.
>> >>     > Another reason why I said that it is not relevant is of
>> course if
>> >>     > someone tries
>> >>     > reconfigure the interface through network-scripts.
>> >>
>> >>     well, honestly I did that (modified ifcfg and then use nmcli con
>> >>     reload). So right way is using nmcli con modify command?
>> >>
>> >>
>> >> Yes or nmstate. Just be aware that anything that you do to interface
>> >> outside of oVirt can have harmful impacts on the host and overall
>> oVirt
>> >> state.
>> >>  
>> >>
>> >>
>> >>     >     from nmstatectl show I can see that bond0 has specified mac
>> >>     address
>> >>     >
>> >>     >   
>> >>   
>>   
>> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
>> >>     >
>> >>     >     >     BONDING_OPTS="active_slave=ens5 downdelay=0
>> miimon=100
>> >>     >     >     mode=active-backup primary=ens5 updelay=0"
>> >>     >     >     TYPE=Bond
>> >>     >     >     BONDING_MASTER=yes
>> >>     >     >     PROXY_METHOD=none
>> >>     >     >     BROWSER_ONLY=no
>> >>     >     >     IPV4_FAILURE_FATAL=no
>> >>     >     >     IPV6_DISABLED=yes
>> >>     >     >     IPV6INIT=no
>> >>     >     >     NAME=bond0
>> >>     >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
>> >>     >     >     DEVICE=bond0
>> >>     >     >     ONBOOT=yes
>> >>     >     >     MTU=9000
>> >>     >     >
>> >>     >     >     When I try to add a custom parameter
>> "fail_over_mac=active"
>> >>     >     (which I
>> >>     >     >     believe could solve my problems with stalled mac
>> >>     addresses in
>> >>     >     switch's
>> >>     >     >     cam table in case of failover) I got...
>> >>     >     >
>> >>     >     >     "Error while executing action HostSetupNetworks:
>> Unexpected
>> >>     >     exception"
>> >>     >     >
>> >>     >     >     ...in manager. In the engine.log it looks like
>> >>     >     >
>> >>     >     >     2020-07-22 21:20:35,774+02 WARN
>> >>     > 

[ovirt-users] Re: problem with custom bond options

2020-07-24 Thread Jiří Sléžka
On 7/24/20 10:56 AM, Ales Musil wrote:
> 
> 
> On Fri, Jul 24, 2020 at 10:40 AM Jiří Sléžka  > wrote:
> 
> On 7/23/20 2:07 PM, Jiří Sléžka wrote:
> > On 7/23/20 12:35 PM, Ales Musil wrote:
> >>
> >>
> >> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka  
> >> >> wrote:
> >>
> >>     On 7/23/20 11:03 AM, Ales Musil wrote:
> >>     >
> >>     >
> >>     > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka
> mailto:jiri.sle...@slu.cz>
> >>     >
> >>     > 
>  >>     >
> >>     >     Hi,
> >>     >
> >>     >     On 7/23/20 8:38 AM, Ales Musil wrote:
> >>     >     >
> >>     >     >
> >>     >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
> >>     mailto:jiri.sle...@slu.cz>
> >
> >>     >     
> >>
> >>     >     >    >
> >>     
>  wrote:
> >>     >     >
> >>     >     >     Hello,
> >>     >     >
> >>     >     >
> >>     >     > Hi,
> >>     >     >
> >>     >     >
> >>     >     >     CentOS8, oVirt 4.4.1.10-1.el8
> >>     >     >
> >>     >     >     I am trying to setup active-backup (mode=1)
> bonding mode
> >>     with
> >>     >     custom
> >>     >     >     properties. I have one 10GE switch, the second is
> just 1G.
> >>     >     10GE link is
> >>     >     >     the primary one.
> >>     >     >
> >>     >     >     cat /etc/sysconfig/network-scripts/ifcfg-bond0
> >>     >     >
> >>     >     >
> >>     >     > first of all in oVirt 4.4 the network-scripts are not
> relevant
> >>     >     anymore.
> >>     >     > More relevant is output from 'nmstatectl show'.
> >>     >
> >>     >     thanks, I believed that ifcfg files still describes saved
> >>     interface
> >>     >     configuration (even on nm managed interfaces)...
> >>     >
> >>     >
> >>     > It does but it might not be that detailed as we would have
> hoped for.
> >>     > Another reason why I said that it is not relevant is of
> course if
> >>     > someone tries
> >>     > reconfigure the interface through network-scripts.
> >>
> >>     well, honestly I did that (modified ifcfg and then use nmcli con
> >>     reload). So right way is using nmcli con modify command?
> >>
> >>
> >> Yes or nmstate. Just be aware that anything that you do to interface
> >> outside of oVirt can have harmful impacts on the host and overall
> oVirt
> >> state.
> >>  
> >>
> >>
> >>     >     from nmstatectl show I can see that bond0 has specified mac
> >>     address
> >>     >
> >>     >   
> >>   
>   
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
> >>     >
> >>     >     >     BONDING_OPTS="active_slave=ens5 downdelay=0
> miimon=100
> >>     >     >     mode=active-backup primary=ens5 updelay=0"
> >>     >     >     TYPE=Bond
> >>     >     >     BONDING_MASTER=yes
> >>     >     >     PROXY_METHOD=none
> >>     >     >     BROWSER_ONLY=no
> >>     >     >     IPV4_FAILURE_FATAL=no
> >>     >     >     IPV6_DISABLED=yes
> >>     >     >     IPV6INIT=no
> >>     >     >     NAME=bond0
> >>     >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> >>     >     >     DEVICE=bond0
> >>     >     >     ONBOOT=yes
> >>     >     >     MTU=9000
> >>     >     >
> >>     >     >     When I try to add a custom parameter
> "fail_over_mac=active"
> >>     >     (which I
> >>     >     >     believe could solve my problems with stalled mac
> >>     addresses in
> >>     >     switch's
> >>     >     >     cam table in case of failover) I got...
> >>     >     >
> >>     >     >     "Error while executing action HostSetupNetworks:
> Unexpected
> >>     >     exception"
> >>     >     >
> >>     >     >     ...in manager. In the engine.log it looks like
> >>     >     >
> >>     >     >     2020-07-22 21:20:35,774+02 WARN
> >>     >     >   
> >>     >   
> >>   
>    [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >>     >     >     (default task-8)
>  

[ovirt-users] Re: problem with custom bond options

2020-07-24 Thread Ales Musil
On Fri, Jul 24, 2020 at 10:40 AM Jiří Sléžka  wrote:

> On 7/23/20 2:07 PM, Jiří Sléžka wrote:
> > On 7/23/20 12:35 PM, Ales Musil wrote:
> >>
> >>
> >> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka  >> > wrote:
> >>
> >> On 7/23/20 11:03 AM, Ales Musil wrote:
> >> >
> >> >
> >> > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka  >> 
> >> > >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > On 7/23/20 8:38 AM, Ales Musil wrote:
> >> > >
> >> > >
> >> > > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
> >> mailto:jiri.sle...@slu.cz>
> >> > >
> >> > > 
> >>  >> > >
> >> > > Hello,
> >> > >
> >> > >
> >> > > Hi,
> >> > >
> >> > >
> >> > > CentOS8, oVirt 4.4.1.10-1.el8
> >> > >
> >> > > I am trying to setup active-backup (mode=1) bonding mode
> >> with
> >> > custom
> >> > > properties. I have one 10GE switch, the second is just
> 1G.
> >> > 10GE link is
> >> > > the primary one.
> >> > >
> >> > > cat /etc/sysconfig/network-scripts/ifcfg-bond0
> >> > >
> >> > >
> >> > > first of all in oVirt 4.4 the network-scripts are not
> relevant
> >> > anymore.
> >> > > More relevant is output from 'nmstatectl show'.
> >> >
> >> > thanks, I believed that ifcfg files still describes saved
> >> interface
> >> > configuration (even on nm managed interfaces)...
> >> >
> >> >
> >> > It does but it might not be that detailed as we would have hoped
> for.
> >> > Another reason why I said that it is not relevant is of course if
> >> > someone tries
> >> > reconfigure the interface through network-scripts.
> >>
> >> well, honestly I did that (modified ifcfg and then use nmcli con
> >> reload). So right way is using nmcli con modify command?
> >>
> >>
> >> Yes or nmstate. Just be aware that anything that you do to interface
> >> outside of oVirt can have harmful impacts on the host and overall oVirt
> >> state.
> >>
> >>
> >>
> >> > from nmstatectl show I can see that bond0 has specified mac
> >> address
> >> >
> >> >
> >>
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
> >> >
> >> > > BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> >> > > mode=active-backup primary=ens5 updelay=0"
> >> > > TYPE=Bond
> >> > > BONDING_MASTER=yes
> >> > > PROXY_METHOD=none
> >> > > BROWSER_ONLY=no
> >> > > IPV4_FAILURE_FATAL=no
> >> > > IPV6_DISABLED=yes
> >> > > IPV6INIT=no
> >> > > NAME=bond0
> >> > > UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> >> > > DEVICE=bond0
> >> > > ONBOOT=yes
> >> > > MTU=9000
> >> > >
> >> > > When I try to add a custom parameter
> "fail_over_mac=active"
> >> > (which I
> >> > > believe could solve my problems with stalled mac
> >> addresses in
> >> > switch's
> >> > > cam table in case of failover) I got...
> >> > >
> >> > > "Error while executing action HostSetupNetworks:
> Unexpected
> >> > exception"
> >> > >
> >> > > ...in manager. In the engine.log it looks like
> >> > >
> >> > > 2020-07-22 21:20:35,774+02 WARN
> >> > >
> >> >
> >>
>[org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> >> Unexpected
> >> > > return value: Status [code=-32603, message=Internal
> JSON-RPC
> >> > error:
> >> > > {'reason': 'MAC address cannot be specified in bond
> >> interface
> >> > along with
> >> > > specified bond options'}]
> >> > > 2020-07-22 21:20:35,774+02 ERROR
> >> > >
> >> >
> >>
>[org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> >> Failed in
> >> > > 'HostSetupNetworksVDS' method
> >> > > 2020-07-22 21:20:35,774+02 WARN
> >> > >
> >> >
> >>
>[org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> >> Unexpected
> >> > > return value: Status [code=-32603, message=Internal
> JSON-RPC
> >> > error:
> >>

[ovirt-users] Re: problem with custom bond options

2020-07-24 Thread Jiří Sléžka
On 7/23/20 2:07 PM, Jiří Sléžka wrote:
> On 7/23/20 12:35 PM, Ales Musil wrote:
>>
>>
>> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka > > wrote:
>>
>> On 7/23/20 11:03 AM, Ales Musil wrote:
>> >
>> >
>> > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka > 
>> > >> wrote:
>> >
>> >     Hi,
>> >
>> >     On 7/23/20 8:38 AM, Ales Musil wrote:
>> >     >
>> >     >
>> >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
>> mailto:jiri.sle...@slu.cz>
>> >     >
>> >     > 
>> > >     >
>> >     >     Hello,
>> >     >
>> >     >
>> >     > Hi,
>> >     >
>> >     >
>> >     >     CentOS8, oVirt 4.4.1.10-1.el8
>> >     >
>> >     >     I am trying to setup active-backup (mode=1) bonding mode
>> with
>> >     custom
>> >     >     properties. I have one 10GE switch, the second is just 1G.
>> >     10GE link is
>> >     >     the primary one.
>> >     >
>> >     >     cat /etc/sysconfig/network-scripts/ifcfg-bond0
>> >     >
>> >     >
>> >     > first of all in oVirt 4.4 the network-scripts are not relevant
>> >     anymore.
>> >     > More relevant is output from 'nmstatectl show'.
>> >
>> >     thanks, I believed that ifcfg files still describes saved
>> interface
>> >     configuration (even on nm managed interfaces)...
>> >
>> >
>> > It does but it might not be that detailed as we would have hoped for.
>> > Another reason why I said that it is not relevant is of course if
>> > someone tries
>> > reconfigure the interface through network-scripts.
>>
>> well, honestly I did that (modified ifcfg and then use nmcli con
>> reload). So right way is using nmcli con modify command?
>>
>>
>> Yes or nmstate. Just be aware that anything that you do to interface
>> outside of oVirt can have harmful impacts on the host and overall oVirt
>> state.
>>  
>>
>>
>> >     from nmstatectl show I can see that bond0 has specified mac
>> address
>> >
>> >   
>>  
>> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
>> >
>> >     >     BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
>> >     >     mode=active-backup primary=ens5 updelay=0"
>> >     >     TYPE=Bond
>> >     >     BONDING_MASTER=yes
>> >     >     PROXY_METHOD=none
>> >     >     BROWSER_ONLY=no
>> >     >     IPV4_FAILURE_FATAL=no
>> >     >     IPV6_DISABLED=yes
>> >     >     IPV6INIT=no
>> >     >     NAME=bond0
>> >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
>> >     >     DEVICE=bond0
>> >     >     ONBOOT=yes
>> >     >     MTU=9000
>> >     >
>> >     >     When I try to add a custom parameter "fail_over_mac=active"
>> >     (which I
>> >     >     believe could solve my problems with stalled mac
>> addresses in
>> >     switch's
>> >     >     cam table in case of failover) I got...
>> >     >
>> >     >     "Error while executing action HostSetupNetworks: Unexpected
>> >     exception"
>> >     >
>> >     >     ...in manager. In the engine.log it looks like
>> >     >
>> >     >     2020-07-22 21:20:35,774+02 WARN
>> >     >   
>> >   
>>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
>> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
>> Unexpected
>> >     >     return value: Status [code=-32603, message=Internal JSON-RPC
>> >     error:
>> >     >     {'reason': 'MAC address cannot be specified in bond
>> interface
>> >     along with
>> >     >     specified bond options'}]
>> >     >     2020-07-22 21:20:35,774+02 ERROR
>> >     >   
>> >   
>>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
>> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
>> Failed in
>> >     >     'HostSetupNetworksVDS' method
>> >     >     2020-07-22 21:20:35,774+02 WARN
>> >     >   
>> >   
>>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
>> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
>> Unexpected
>> >     >     return value: Status [code=-32603, message=Internal JSON-RPC
>> >     error:
>> >     >     {'reason': 'MAC address cannot be specified in bond
>> interface
>> >     along with
>> >     >     specified bond options'}]
>> >     >     2020-07-22 21:20:35,811+02 ERROR
>> >     >   
>> >   
>>   

[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Jiří Sléžka
On 7/23/20 12:35 PM, Ales Musil wrote:
> 
> 
> On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka  > wrote:
> 
> On 7/23/20 11:03 AM, Ales Musil wrote:
> >
> >
> > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka  
> > >> wrote:
> >
> >     Hi,
> >
> >     On 7/23/20 8:38 AM, Ales Musil wrote:
> >     >
> >     >
> >     > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka
> mailto:jiri.sle...@slu.cz>
> >     >
> >     > 
>  >     >
> >     >     Hello,
> >     >
> >     >
> >     > Hi,
> >     >
> >     >
> >     >     CentOS8, oVirt 4.4.1.10-1.el8
> >     >
> >     >     I am trying to setup active-backup (mode=1) bonding mode
> with
> >     custom
> >     >     properties. I have one 10GE switch, the second is just 1G.
> >     10GE link is
> >     >     the primary one.
> >     >
> >     >     cat /etc/sysconfig/network-scripts/ifcfg-bond0
> >     >
> >     >
> >     > first of all in oVirt 4.4 the network-scripts are not relevant
> >     anymore.
> >     > More relevant is output from 'nmstatectl show'.
> >
> >     thanks, I believed that ifcfg files still describes saved
> interface
> >     configuration (even on nm managed interfaces)...
> >
> >
> > It does but it might not be that detailed as we would have hoped for.
> > Another reason why I said that it is not relevant is of course if
> > someone tries
> > reconfigure the interface through network-scripts.
> 
> well, honestly I did that (modified ifcfg and then use nmcli con
> reload). So right way is using nmcli con modify command?
> 
> 
> Yes or nmstate. Just be aware that anything that you do to interface
> outside of oVirt can have harmful impacts on the host and overall oVirt
> state.
>  
> 
> 
> >     from nmstatectl show I can see that bond0 has specified mac
> address
> >
> >   
>  
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
> >
> >     >     BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> >     >     mode=active-backup primary=ens5 updelay=0"
> >     >     TYPE=Bond
> >     >     BONDING_MASTER=yes
> >     >     PROXY_METHOD=none
> >     >     BROWSER_ONLY=no
> >     >     IPV4_FAILURE_FATAL=no
> >     >     IPV6_DISABLED=yes
> >     >     IPV6INIT=no
> >     >     NAME=bond0
> >     >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> >     >     DEVICE=bond0
> >     >     ONBOOT=yes
> >     >     MTU=9000
> >     >
> >     >     When I try to add a custom parameter "fail_over_mac=active"
> >     (which I
> >     >     believe could solve my problems with stalled mac
> addresses in
> >     switch's
> >     >     cam table in case of failover) I got...
> >     >
> >     >     "Error while executing action HostSetupNetworks: Unexpected
> >     exception"
> >     >
> >     >     ...in manager. In the engine.log it looks like
> >     >
> >     >     2020-07-22 21:20:35,774+02 WARN
> >     >   
> >   
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> Unexpected
> >     >     return value: Status [code=-32603, message=Internal JSON-RPC
> >     error:
> >     >     {'reason': 'MAC address cannot be specified in bond
> interface
> >     along with
> >     >     specified bond options'}]
> >     >     2020-07-22 21:20:35,774+02 ERROR
> >     >   
> >   
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> Failed in
> >     >     'HostSetupNetworksVDS' method
> >     >     2020-07-22 21:20:35,774+02 WARN
> >     >   
> >   
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> Unexpected
> >     >     return value: Status [code=-32603, message=Internal JSON-RPC
> >     error:
> >     >     {'reason': 'MAC address cannot be specified in bond
> interface
> >     along with
> >     >     specified bond options'}]
> >     >     2020-07-22 21:20:35,811+02 ERROR
> >     >   
> >   
>   [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >     >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> EVENT_ID:
> >     >     VDS_BROKER_COMMAND_FAILURE(10,802), 

[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Ales Musil
On Thu, Jul 23, 2020 at 11:50 AM Jiří Sléžka  wrote:

> On 7/23/20 11:03 AM, Ales Musil wrote:
> >
> >
> > On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka  > > wrote:
> >
> > Hi,
> >
> > On 7/23/20 8:38 AM, Ales Musil wrote:
> > >
> > >
> > > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka  > 
> > > >> wrote:
> > >
> > > Hello,
> > >
> > >
> > > Hi,
> > >
> > >
> > > CentOS8, oVirt 4.4.1.10-1.el8
> > >
> > > I am trying to setup active-backup (mode=1) bonding mode with
> > custom
> > > properties. I have one 10GE switch, the second is just 1G.
> > 10GE link is
> > > the primary one.
> > >
> > > cat /etc/sysconfig/network-scripts/ifcfg-bond0
> > >
> > >
> > > first of all in oVirt 4.4 the network-scripts are not relevant
> > anymore.
> > > More relevant is output from 'nmstatectl show'.
> >
> > thanks, I believed that ifcfg files still describes saved interface
> > configuration (even on nm managed interfaces)...
> >
> >
> > It does but it might not be that detailed as we would have hoped for.
> > Another reason why I said that it is not relevant is of course if
> > someone tries
> > reconfigure the interface through network-scripts.
>
> well, honestly I did that (modified ifcfg and then use nmcli con
> reload). So right way is using nmcli con modify command?
>

Yes or nmstate. Just be aware that anything that you do to interface
outside of oVirt can have harmful impacts on the host and overall oVirt
state.


>
> > from nmstatectl show I can see that bond0 has specified mac address
> >
> >
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
> >
> > > BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> > > mode=active-backup primary=ens5 updelay=0"
> > > TYPE=Bond
> > > BONDING_MASTER=yes
> > > PROXY_METHOD=none
> > > BROWSER_ONLY=no
> > > IPV4_FAILURE_FATAL=no
> > > IPV6_DISABLED=yes
> > > IPV6INIT=no
> > > NAME=bond0
> > > UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> > > DEVICE=bond0
> > > ONBOOT=yes
> > > MTU=9000
> > >
> > > When I try to add a custom parameter "fail_over_mac=active"
> > (which I
> > > believe could solve my problems with stalled mac addresses in
> > switch's
> > > cam table in case of failover) I got...
> > >
> > > "Error while executing action HostSetupNetworks: Unexpected
> > exception"
> > >
> > > ...in manager. In the engine.log it looks like
> > >
> > > 2020-07-22 21:20:35,774+02 WARN
> > >
> >
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> Unexpected
> > > return value: Status [code=-32603, message=Internal JSON-RPC
> > error:
> > > {'reason': 'MAC address cannot be specified in bond interface
> > along with
> > > specified bond options'}]
> > > 2020-07-22 21:20:35,774+02 ERROR
> > >
> >
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed
> in
> > > 'HostSetupNetworksVDS' method
> > > 2020-07-22 21:20:35,774+02 WARN
> > >
> >
>   [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> Unexpected
> > > return value: Status [code=-32603, message=Internal JSON-RPC
> > error:
> > > {'reason': 'MAC address cannot be specified in bond interface
> > along with
> > > specified bond options'}]
> > > 2020-07-22 21:20:35,811+02 ERROR
> > >
> >
>   [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> > > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0]
> EVENT_ID:
> > > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local
> > command
> > > HostSetupNetworksVDS failed: Internal JSON-RPC error:
> > {'reason': 'MAC
> > > address cannot be specified in bond interface along with
> > specified bond
> > > options'}
> > >
> > >
> > > Can you please share supervdsm.log from the relevant host?
> >
> > here it is
> >
> >
> https://paste.slu.cz/?ef8bd7eeae8eeaed#Ej3MXRufm6Y9qjKCkgCXXieP132kRAiswR17ygxQDhft
> >
> >
> > This indeed seems to be a bug. Can you please open BZ
> > ?
>
> done
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1859890
>
> > Only workaround that comes to my mind is to break the bond and define it
> > again with specified mode.
>
> just for sure - do you mean on 

[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Jiří Sléžka
On 7/23/20 11:03 AM, Ales Musil wrote:
> 
> 
> On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka  > wrote:
> 
> Hi,
> 
> On 7/23/20 8:38 AM, Ales Musil wrote:
> >
> >
> > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka  
> > >> wrote:
> >
> >     Hello,
> >
> >
> > Hi,
> >
> >
> >     CentOS8, oVirt 4.4.1.10-1.el8
> >
> >     I am trying to setup active-backup (mode=1) bonding mode with
> custom
> >     properties. I have one 10GE switch, the second is just 1G.
> 10GE link is
> >     the primary one.
> >
> >     cat /etc/sysconfig/network-scripts/ifcfg-bond0
> >
> >
> > first of all in oVirt 4.4 the network-scripts are not relevant
> anymore.
> > More relevant is output from 'nmstatectl show'.
> 
> thanks, I believed that ifcfg files still describes saved interface
> configuration (even on nm managed interfaces)...
> 
> 
> It does but it might not be that detailed as we would have hoped for.
> Another reason why I said that it is not relevant is of course if
> someone tries
> reconfigure the interface through network-scripts.

well, honestly I did that (modified ifcfg and then use nmcli con
reload). So right way is using nmcli con modify command?

> from nmstatectl show I can see that bond0 has specified mac address
> 
> 
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
> 
> >     BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> >     mode=active-backup primary=ens5 updelay=0"
> >     TYPE=Bond
> >     BONDING_MASTER=yes
> >     PROXY_METHOD=none
> >     BROWSER_ONLY=no
> >     IPV4_FAILURE_FATAL=no
> >     IPV6_DISABLED=yes
> >     IPV6INIT=no
> >     NAME=bond0
> >     UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> >     DEVICE=bond0
> >     ONBOOT=yes
> >     MTU=9000
> >
> >     When I try to add a custom parameter "fail_over_mac=active"
> (which I
> >     believe could solve my problems with stalled mac addresses in
> switch's
> >     cam table in case of failover) I got...
> >
> >     "Error while executing action HostSetupNetworks: Unexpected
> exception"
> >
> >     ...in manager. In the engine.log it looks like
> >
> >     2020-07-22 21:20:35,774+02 WARN
> >   
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> >     return value: Status [code=-32603, message=Internal JSON-RPC
> error:
> >     {'reason': 'MAC address cannot be specified in bond interface
> along with
> >     specified bond options'}]
> >     2020-07-22 21:20:35,774+02 ERROR
> >   
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed in
> >     'HostSetupNetworksVDS' method
> >     2020-07-22 21:20:35,774+02 WARN
> >   
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> >     return value: Status [code=-32603, message=Internal JSON-RPC
> error:
> >     {'reason': 'MAC address cannot be specified in bond interface
> along with
> >     specified bond options'}]
> >     2020-07-22 21:20:35,811+02 ERROR
> >   
>  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> >     (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] EVENT_ID:
> >     VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local
> command
> >     HostSetupNetworksVDS failed: Internal JSON-RPC error:
> {'reason': 'MAC
> >     address cannot be specified in bond interface along with
> specified bond
> >     options'}
> >
> >
> > Can you please share supervdsm.log from the relevant host?
> 
> here it is
> 
> 
> https://paste.slu.cz/?ef8bd7eeae8eeaed#Ej3MXRufm6Y9qjKCkgCXXieP132kRAiswR17ygxQDhft
> 
> 
> This indeed seems to be a bug. Can you please open BZ
> ?

done

https://bugzilla.redhat.com/show_bug.cgi?id=1859890

> Only workaround that comes to my mind is to break the bond and define it
> again with specified mode.

just for sure - do you mean on the live host which hosts running HE vm
or on a new installation?

It looks like there is the same o similar bug while installing hosted
engine via ovirt-hosted-engine-setup. I tried it many times yesterday
and installation failed with the same error

[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg": "The
host has been set in non_operational status, deployment errors:   code
505: Host ovirt-hci01.stud.slu.cz 

[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Ales Musil
On Thu, Jul 23, 2020 at 10:35 AM Jiří Sléžka  wrote:

> Hi,
>
> On 7/23/20 8:38 AM, Ales Musil wrote:
> >
> >
> > On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka  > > wrote:
> >
> > Hello,
> >
> >
> > Hi,
> >
> >
> > CentOS8, oVirt 4.4.1.10-1.el8
> >
> > I am trying to setup active-backup (mode=1) bonding mode with custom
> > properties. I have one 10GE switch, the second is just 1G. 10GE link
> is
> > the primary one.
> >
> > cat /etc/sysconfig/network-scripts/ifcfg-bond0
> >
> >
> > first of all in oVirt 4.4 the network-scripts are not relevant anymore.
> > More relevant is output from 'nmstatectl show'.
>
> thanks, I believed that ifcfg files still describes saved interface
> configuration (even on nm managed interfaces)...
>

It does but it might not be that detailed as we would have hoped for.
Another reason why I said that it is not relevant is of course if someone
tries
reconfigure the interface through network-scripts.


>
> from nmstatectl show I can see that bond0 has specified mac address
>
>
> https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka
>
> > BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> > mode=active-backup primary=ens5 updelay=0"
> > TYPE=Bond
> > BONDING_MASTER=yes
> > PROXY_METHOD=none
> > BROWSER_ONLY=no
> > IPV4_FAILURE_FATAL=no
> > IPV6_DISABLED=yes
> > IPV6INIT=no
> > NAME=bond0
> > UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> > DEVICE=bond0
> > ONBOOT=yes
> > MTU=9000
> >
> > When I try to add a custom parameter "fail_over_mac=active" (which I
> > believe could solve my problems with stalled mac addresses in
> switch's
> > cam table in case of failover) I got...
> >
> > "Error while executing action HostSetupNetworks: Unexpected
> exception"
> >
> > ...in manager. In the engine.log it looks like
> >
> > 2020-07-22 21:20:35,774+02 WARN
> >
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> > return value: Status [code=-32603, message=Internal JSON-RPC error:
> > {'reason': 'MAC address cannot be specified in bond interface along
> with
> > specified bond options'}]
> > 2020-07-22 21:20:35,774+02 ERROR
> >
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed in
> > 'HostSetupNetworksVDS' method
> > 2020-07-22 21:20:35,774+02 WARN
> >
>  [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> > return value: Status [code=-32603, message=Internal JSON-RPC error:
> > {'reason': 'MAC address cannot be specified in bond interface along
> with
> > specified bond options'}]
> > 2020-07-22 21:20:35,811+02 ERROR
> >
>  [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> > (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] EVENT_ID:
> > VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local
> command
> > HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'MAC
> > address cannot be specified in bond interface along with specified
> bond
> > options'}
> >
> >
> > Can you please share supervdsm.log from the relevant host?
>
> here it is
>
>
> https://paste.slu.cz/?ef8bd7eeae8eeaed#Ej3MXRufm6Y9qjKCkgCXXieP132kRAiswR17ygxQDhft


This indeed seems to be a bug. Can you please open BZ
?

Only workaround that comes to my mind is to break the bond and define it
again with specified mode.

Let me know if it works.

Thanks,
Ales


>
>
> Cheers,
>
> Jiri
>
>
> > Could anybody explain me what 'MAC address cannot be specified in
> bond
> > interface along with specified bond options' means? I believe a MAC
> > address is not configured in interface configuration.
> >
> > Or does it mean 'fail_over_mac=active' is not supported in oVirt?
> >
> > Thanks in advance,
> >
> > Jiri
> >
> >
> >
> >
> >
> > ___
> > Users mailing list -- users@ovirt.org 
> > To unsubscribe send an email to users-le...@ovirt.org
> > 
> > Privacy Statement: https://www.ovirt.org/privacy-policy.html
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> >
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BUGNSEBD3OBSUPASLJQYYJIF5767XMDE/
> >
> >
> >
> > Thank you.
> > Regards,
> > Ales
> >
> > --
> >
> > Ales Musil
> >
> > Software Engineer - RHV Network
> >
> > Red Hat EMEA 
> >
> > amu...@redhat.com IM: amusil
> >
> > 
> >
>
>
>


[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Jiří Sléžka
Hi,

On 7/23/20 8:38 AM, Ales Musil wrote:
> 
> 
> On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka  > wrote:
> 
> Hello,
> 
> 
> Hi,
> 
> 
> CentOS8, oVirt 4.4.1.10-1.el8
> 
> I am trying to setup active-backup (mode=1) bonding mode with custom
> properties. I have one 10GE switch, the second is just 1G. 10GE link is
> the primary one.
> 
> cat /etc/sysconfig/network-scripts/ifcfg-bond0
> 
> 
> first of all in oVirt 4.4 the network-scripts are not relevant anymore.
> More relevant is output from 'nmstatectl show'.

thanks, I believed that ifcfg files still describes saved interface
configuration (even on nm managed interfaces)...

from nmstatectl show I can see that bond0 has specified mac address

https://paste.slu.cz/?d363cf2c029f6b83#Ew2rCiYyNGrdfffy6bvzSjbb8x4jJsaUdhxkjwThMFka

> BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> mode=active-backup primary=ens5 updelay=0"
> TYPE=Bond
> BONDING_MASTER=yes
> PROXY_METHOD=none
> BROWSER_ONLY=no
> IPV4_FAILURE_FATAL=no
> IPV6_DISABLED=yes
> IPV6INIT=no
> NAME=bond0
> UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> DEVICE=bond0
> ONBOOT=yes
> MTU=9000
> 
> When I try to add a custom parameter "fail_over_mac=active" (which I
> believe could solve my problems with stalled mac addresses in switch's
> cam table in case of failover) I got...
> 
> "Error while executing action HostSetupNetworks: Unexpected exception"
> 
> ...in manager. In the engine.log it looks like
> 
> 2020-07-22 21:20:35,774+02 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> return value: Status [code=-32603, message=Internal JSON-RPC error:
> {'reason': 'MAC address cannot be specified in bond interface along with
> specified bond options'}]
> 2020-07-22 21:20:35,774+02 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed in
> 'HostSetupNetworksVDS' method
> 2020-07-22 21:20:35,774+02 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> return value: Status [code=-32603, message=Internal JSON-RPC error:
> {'reason': 'MAC address cannot be specified in bond interface along with
> specified bond options'}]
> 2020-07-22 21:20:35,811+02 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local command
> HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'MAC
> address cannot be specified in bond interface along with specified bond
> options'}
> 
> 
> Can you please share supervdsm.log from the relevant host?

here it is

https://paste.slu.cz/?ef8bd7eeae8eeaed#Ej3MXRufm6Y9qjKCkgCXXieP132kRAiswR17ygxQDhft

Cheers,

Jiri


> Could anybody explain me what 'MAC address cannot be specified in bond
> interface along with specified bond options' means? I believe a MAC
> address is not configured in interface configuration.
> 
> Or does it mean 'fail_over_mac=active' is not supported in oVirt?
> 
> Thanks in advance,
> 
> Jiri
> 
> 
> 
> 
> 
> ___
> Users mailing list -- users@ovirt.org 
> To unsubscribe send an email to users-le...@ovirt.org
> 
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BUGNSEBD3OBSUPASLJQYYJIF5767XMDE/
> 
> 
> 
> Thank you.
> Regards,
> Ales
> 
> -- 
> 
> Ales Musil
> 
> Software Engineer - RHV Network
> 
> Red Hat EMEA 
> 
> amu...@redhat.com     IM: amusil
> 
> 
> 




smime.p7s
Description: S/MIME Cryptographic Signature
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/YQ5SW7FIHB57UIDB37WEHEIFKZOXVA6F/


[ovirt-users] Re: problem with custom bond options

2020-07-23 Thread Ales Musil
On Wed, Jul 22, 2020 at 9:41 PM Jiří Sléžka  wrote:

> Hello,
>

Hi,


> CentOS8, oVirt 4.4.1.10-1.el8
>
> I am trying to setup active-backup (mode=1) bonding mode with custom
> properties. I have one 10GE switch, the second is just 1G. 10GE link is
> the primary one.
>
> cat /etc/sysconfig/network-scripts/ifcfg-bond0
>

first of all in oVirt 4.4 the network-scripts are not relevant anymore.
More relevant is output from 'nmstatectl show'.


>
> BONDING_OPTS="active_slave=ens5 downdelay=0 miimon=100
> mode=active-backup primary=ens5 updelay=0"
> TYPE=Bond
> BONDING_MASTER=yes
> PROXY_METHOD=none
> BROWSER_ONLY=no
> IPV4_FAILURE_FATAL=no
> IPV6_DISABLED=yes
> IPV6INIT=no
> NAME=bond0
> UUID=c054364e-47cf-47ee-a7fc-70b37c9977e7
> DEVICE=bond0
> ONBOOT=yes
> MTU=9000
>
> When I try to add a custom parameter "fail_over_mac=active" (which I
> believe could solve my problems with stalled mac addresses in switch's
> cam table in case of failover) I got...
>
> "Error while executing action HostSetupNetworks: Unexpected exception"
>
> ...in manager. In the engine.log it looks like
>
> 2020-07-22 21:20:35,774+02 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> return value: Status [code=-32603, message=Internal JSON-RPC error:
> {'reason': 'MAC address cannot be specified in bond interface along with
> specified bond options'}]
> 2020-07-22 21:20:35,774+02 ERROR
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Failed in
> 'HostSetupNetworksVDS' method
> 2020-07-22 21:20:35,774+02 WARN
> [org.ovirt.engine.core.vdsbroker.vdsbroker.HostSetupNetworksVDSCommand]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] Unexpected
> return value: Status [code=-32603, message=Internal JSON-RPC error:
> {'reason': 'MAC address cannot be specified in bond interface along with
> specified bond options'}]
> 2020-07-22 21:20:35,811+02 ERROR
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
> (default task-8) [da1984f3-f38b-4e0a-ac80-a81e67d73ff0] EVENT_ID:
> VDS_BROKER_COMMAND_FAILURE(10,802), VDSM ovirt-hci01.mch.local command
> HostSetupNetworksVDS failed: Internal JSON-RPC error: {'reason': 'MAC
> address cannot be specified in bond interface along with specified bond
> options'}
>
>
Can you please share supervdsm.log from the relevant host?


>
> Could anybody explain me what 'MAC address cannot be specified in bond
> interface along with specified bond options' means? I believe a MAC
> address is not configured in interface configuration.
>
> Or does it mean 'fail_over_mac=active' is not supported in oVirt?
>
> Thanks in advance,
>
> Jiri
>
>
>
>
>
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/BUGNSEBD3OBSUPASLJQYYJIF5767XMDE/
>


Thank you.
Regards,
Ales

-- 

Ales Musil

Software Engineer - RHV Network

Red Hat EMEA 

amu...@redhat.comIM: amusil

___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/32UM7RWI5WAN2L2OT7D4PZLCBUWVLDQZ/