netlink speed check fail , "invalid argument"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NRPE Charm |
New
|
Undecided
|
Unassigned |
Bug Description
when netlinks option is configured , nagios calls check_netlink in remote host to check interface information
# nagios command
/usr/lib/
currently check_netlinks.py check link mtu and speed by reading files from /sys/class/
For example , in Kubernetes deployment that use Juniper contrail CNI , contrail charm will create a vhost0 interface which has mtu but no speed information
19: vhost0: <BROADCAST,
link/ether 48:df:37:9b:90:68 brd ff:ff:ff:ff:ff:ff
ubuntu@
9000
ubuntu@
cat: /sys/class/
In this case , the check_netlinks.py will fail
ubuntu@
CRITICAL: vhost0 (speed returns invalid argument)
Although not function impacting, Nagios will show critical alarm on this interface
One potential solution is to do speed check only when the option is specified in nrpe netlinks config options, or give user option exclude certain link from speed check
Relevant nrpe config:
ubuntu@
- vhost0 mtu:9000 op:unknown
- < other interface config, skipped >