Description
In current software, it appears that gbsyncd restart is required when syncd and swss services restart manually or due to a failure. If gbsyncd service does not restart, swss keeps failing until systemd puts the service in failed state. It appears that gbsyncd is required to be restarted when swss restart, like syncd which is restated every time swss restarts.
This bug is to investigate the swss - gbsyncd interdependency and remove any dependency if possible, otherwise define systemd and peer service dependency properly for restartability.
gbsyncd is not defined as restartable process in systemd, that also needs to be fixed if required for restart capability.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of show version:
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):
Description
In current software, it appears that gbsyncd restart is required when syncd and swss services restart manually or due to a failure. If gbsyncd service does not restart, swss keeps failing until systemd puts the service in failed state. It appears that gbsyncd is required to be restarted when swss restart, like syncd which is restated every time swss restarts.
This bug is to investigate the swss - gbsyncd interdependency and remove any dependency if possible, otherwise define systemd and peer service dependency properly for restartability.
gbsyncd is not defined as restartable process in systemd, that also needs to be fixed if required for restart capability.
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Output of
show version:Output of
show techsupport:Additional information you deem important (e.g. issue happens only occasionally):