Adding "bond" to the grep will prevent the error occurence, but it has a side effect of not showing the IP of the bond interface and listing the device as "Not-Networked." Another unintended result is that only the current active interface in an active-backup bond is even listed.
I do acknowledge the error issue but don't think this is the best way to fix it. I spun up some VMs with difference bond settings so that I can work on a fix.
As for the "OUT OF SPEC," that happens when you have an old version of dmidecode. I have already made at least one "OUT OF SPEC" exception elsewhere:
529 system_form_factor=`$OA_DMIDECODE -s chassis-type`
530 if [ "$system_form_factor" = "<OUT OF SPEC>" ]; then
531 system_form_factor="Unknown"
532 fi
I'll have to come up with a better way of handling "OUT OF SPEC" from dmidecode without having to set that "if" on every single instance of dmidecode output.
Adding "bond" to the grep will prevent the error occurence, but it has a side effect of not showing the IP of the bond interface and listing the device as "Not-Networked." Another unintended result is that only the current active interface in an active-backup bond is even listed.
I do acknowledge the error issue but don't think this is the best way to fix it. I spun up some VMs with difference bond settings so that I can work on a fix.
As for the "OUT OF SPEC," that happens when you have an old version of dmidecode. I have already made at least one "OUT OF SPEC" exception elsewhere:
529 system_ form_factor= `$OA_DMIDECODE -s chassis-type` form_factor" = "<OUT OF SPEC>" ]; then form_factor= "Unknown"
530 if [ "$system_
531 system_
532 fi
I'll have to come up with a better way of handling "OUT OF SPEC" from dmidecode without having to set that "if" on every single instance of dmidecode output.