The voq system lag id boundary is set in redis-chassis. Changes include setting this from database-chassis container. This fixes a timing issue in finding datbase_config.json file from redis directory which is created from database container. Since database container usually starts after database-chassis container the existence of this file is unreliable while running the command. Running the command under database-chassis container makes sure that the database_config.json form redis-chassis directory is guaranteed to be available and hence fixes the timing issue. Signed-off-by: vedganes <vedavinayagam.ganesan@nokia.com> |
||
---|---|---|
.. | ||
per_namespace | ||
share_image | ||
arp_update_vars.j2 | ||
buffers_config.j2 | ||
config-chassisdb.service.j2 | ||
config-setup.service.j2 | ||
database.service.j2 | ||
dhcp_relay.service.j2 | ||
docker_image_ctl.j2 | ||
gbsyncd.service.j2 | ||
iccpd.service.j2 | ||
init_cfg.json.j2 | ||
kube_cni.10-flannel.conflist | ||
lldp.service.j2 | ||
macsec.service.j2 | ||
manifest.json.j2 | ||
mgmt-framework.service.j2 | ||
mgmt-framework.timer | ||
nat.service.j2 | ||
organization_extensions.sh | ||
packages.json.j2 | ||
pmon.service.j2 | ||
qos_config.j2 | ||
radv.service.j2 | ||
restapi.service.j2 | ||
sflow.service.j2 | ||
snmp.service.j2 | ||
snmp.timer | ||
sonic_debian_extension.j2 | ||
sonic_version.yml.j2 | ||
sonic-delayed.target | ||
sonic.target | ||
swss_vars.j2 | ||
tacacs-config.service | ||
tacacs-config.timer | ||
telemetry.service.j2 | ||
telemetry.timer | ||
updategraph.service.j2 |