Open judyjoseph opened 2 years ago
Is the issue on master or 201911 specific?
Prince, this issue is seen in master too
@judyjoseph why do we want to restart when SIGTERM is received? What about service stop flow when supervisord sends SIGTERM by default?
Description
The teamd docker not getting restarted when teamsyncd gets SIGTERM signal
Steps to reproduce the issue:
Describe the results you received:
The teamd docker did not restart.
str2--acs-1 INFO teamd1#supervisord 2022-04-11 18:39:11,420 INFO exited: teamsyncd (exit status 0; expected) str2--acs-1 INFO teamd0#supervisord 2022-04-11 18:38:25,279 INFO exited: teammgrd (exit status 255; not expected)
The teamd docker did exit correct when SIGTERM is send to teammgrd process.
Describe the results you expected:
The teamd docker should restart as teamsyncd is a critical process.
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):