SE log agent crash causes datapath downtime

Products

• VMware Avi Load Balancer

Issue/Introduction

• SE crashes and reboot due to SE log agent crash
• Stack trace: (Crash is available at following path "Administration--> Support --> Crash Reports) 

  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/avi/bin/se_log_agent --log_dir=/var/lib/avi/log/glog'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x00005613577201a2 in std::Hashtable<unsigned int, std::pair<unsigned int const, std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<unsigned int const, std::cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >, std::detail::_Select1st, std::equal_to<unsigned int>, std::hash<unsigned

Environment

Avi version 22.1.6

Resolution

• A fix has been added to Avi versions 30.2.3, 22.1.7-2p5, 30.2.2-2p3, 31.1.1-2p1.
• With the fixed versions, Incase of a log-agent crash, now the SE is not restarted and hence no Datapath will be impacted
• Upgrade Avi LB to any of the fixed versions above.