Checkmk 2.4.0 Parsing of section ovs_bonding failed

Feedback 2.4 Beta
1

Since upgrading to 2.4.0 we get discovery failure warnings for as ucs hosts

image
image899Ă—35 8.7 KB

The agent output looks like:

[...]
<<<ovs_bonding:sep(58)>>>
[bond1]
---- bond1 ----
bond_mode: balance-slb
bond may use recirculation: no, Recirc-ID : -1
bond-hash-basis: 0
updelay: 31000 ms
downdelay: 200 ms
next rebalance: 1542816 ms
lacp_status: off
active slave mac: xx:xx:xx:xx:xx:xx(eth0)

slave eth0: enabled
active slave
may_enable: true
hash 140: 2377 kB load

slave eth1: enabled
may_enable: true

[bond0]
---- bond0 ----
bond_mode: balance-slb
bond may use recirculation: no, Recirc-ID : -1
bond-hash-basis: 0
updelay: 31000 ms
downdelay: 200 ms
next rebalance: 1539313 ms
lacp_status: off
active slave mac: xx:xx:xx:xx:xx:xx(eth5)

slave eth4: enabled
may_enable: true
hash 226: 220936 kB load
hash 246: 215104 kB load
hash 250: 85186 kB load

slave eth5: enabled
active slave
may_enable: true
hash 35: 232299 kB load
hash 36: 352630 kB load
[...]
2

Would it be possible for you to submit the crash report or open an official ticket?

3

Thanks for the hint, I’ve submitted the crash report via the GUI (first time - didn’t know that feature existed at all, provides useful information and that a parse failure counts as a “crash”) .

For completeness here’s the actual error:

  File "/omd/sites/customer/lib/python3/cmk/checkengine/sectionparser.py", line 121, in _parse_raw_data
    return parse_function(list(raw_data))
  File "/omd/sites/customer/lib/python3/cmk/plugins/collection/agent_based/ovs_bonding.py", line 45, in parse_ovs_bonding
    raise InvalidOvsBondingStringTable("Missing slave inteface value.")
Missing slave inteface value.

I hope my email with full details arrived as well. We are currently still in an old contract without the opportunity to have access to the ticket system to be able to open an official ticket.

4

Thanks for the hint, I’ve submitted the crash report via the GUI (first time - didn’t know that feature existed at all, provides useful information and that a parse failure counts as a “crash”)

Thanks for submitting. I can see the crash report and an internal ticket has been opened.
Will keep you posted.

2 Likes
5

Good Morning @tgurr,

the issue should be fixed with this werk: Werk #18141: ovs_bonding: Fix InvalidOvsBondingStringTable (Missing slave inteface value.)

Sunny Greetings
Hartmut

1 Like
6

Hello @tgurr,

have you been able to test the fix?
If yes and it solves your issue, please close this topic.

Sunny Greetings and thank you
Hartmut