0a54c46a0d
Why I did it If the SWSS services was restarted, the MACsec service should also be restarted. Otherwise the data in wpa_supplicant and orchagent will not be consistent. How I did it Add dependency in docker-macsec.mk. How to verify it Manually check by 'sudo service swss restart'. The MACsec container should be started after swss, the syslog will look like Sep 8 14:36:29.562953 sonic INFO swss.sh[9661]: Starting existing swss container with HWSKU Force10-S6000 Sep 8 14:36:30.024399 sonic DEBUG container: container_start: BEGIN ... Sep 8 14:36:33.391706 sonic INFO systemd[1]: Starting macsec container... Sep 8 14:36:33.392925 sonic INFO systemd[1]: Starting Management Framework container... Signed-off-by: Ze Gan <ganze718@gmail.com> |
||
---|---|---|
.. | ||
arp_update | ||
asic_status.py | ||
asic_status.sh | ||
bgp.sh | ||
configdb-load.sh | ||
core_cleanup.py | ||
gbsyncd-platform.sh | ||
gbsyncd.sh | ||
lldp.sh | ||
mark_dhcp_packet.py | ||
radv.sh | ||
sonic-netns-exec | ||
supervisor-proc-exit-listener | ||
swss.sh | ||
syncd_common.sh | ||
syncd.sh | ||
teamd.sh | ||
update_chassisdb_config | ||
write_standby.py |