You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test case container_checker/test_container_checker.py::test_container_checker fail because the log containers not running.*syncd.* was recorded 10 mins after stop syncd
Results you see
Root cause
Base on the logic of test_container_checker, the script will check if the tested container is running before the tested container stop. If the tested container is not running, it will execute config reload to recover the tested container
When swss stop, the syncd also be stopped. So when run the syncd stop test, config reload will be executed firstly to recovery syncd. After config reload, the monit needs takes sometimes to init, which lead to generate message delay
Why the issue does not occur on other containers
In others container stop test, the tested container in running status before the test, no need to do config load, monit no need to re-init, so the message can record in syslog immediately
Next action
After config reload, need use command sudo monit summary make sure monit init ready before do other operations
admin@r-panther-03:~$ sudo monit summary
Monit 5.20.0 uptime: 8h 26m
Service Name Status Type
r-panther-03 Running System
rsyslog Running Process
root-overlay Accessible Filesystem
var-log Accessible Filesystem
routeCheck Status ok Program
dualtorNeighborCheck Status ok Program
diskCheck Status ok Program
container_checker Status ok Program
vnetRouteCheck Status ok Program
memory_check Status ok Program
arp_update_checker Status ok Program
controlPlaneDropCheck Status ok Program
container_memory_snmp Status ok Program
container_memory_gnmi Status ok Program
container_eventd Status ok Program
container_memory_bmp Status ok Program
Results you expected to see
Case always pass
Is it platform specific
generic
Relevant log output
No response
Output of show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered:
Issue Description
Test case
container_checker/test_container_checker.py::test_container_checker
fail because the logcontainers not running.*syncd.*
was recorded 10 mins after stop syncdResults you see
Root cause
Base on the logic of test_container_checker, the script will check if the tested container is running before the tested container stop. If the tested container is not running, it will execute config reload to recover the tested container
When swss stop, the syncd also be stopped. So when run the syncd stop test, config reload will be executed firstly to recovery syncd. After config reload, the monit needs takes sometimes to init, which lead to generate message delay
Why the issue does not occur on other containers
In others container stop test, the tested container in running status before the test, no need to do config load, monit no need to re-init, so the message can record in syslog immediately
Next action
After config reload, need use command
sudo monit summary
make sure monit init ready before do other operationsResults you expected to see
Case always pass
Is it platform specific
generic
Relevant log output
No response
Output of
show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: