The teamd docker not getting restarted when teamsyncd gets SIGTERM signal

[judyjoseph]

Description

The teamd docker not getting restarted when teamsyncd gets SIGTERM signal

Steps to reproduce the issue:

1. Send SIGTERM signal to teamsyncd process in teamd docker
2. Check if teamd docker exists

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:

SONiC Software Version: SONiC.20191130.78
Distribution: Debian 9.13
Kernel: 4.9.0-14-2-amd64
Build commit: 7be7d5b265
Build date: Sat Aug  7 03:26:09 UTC 2021
Built by: AzDevOps@sonic-int-build-workers-0002IO

Output of show techsupport:

(paste your output here or download and attach the file here )

Additional information you deem important (e.g. issue happens only occasionally):

[prsunny]

Is the issue on master or 201911 specific?

[judyjoseph]

Prince, this issue is seen in master too

[nazariig]

@judyjoseph why do we want to restart when SIGTERM is received? What about service stop flow when supervisord sends SIGTERM by default?