- Why I did it The recent change #15685 (comment) removed the db migration for non first reboots. This is problematic for many deployments which doesn't rely on ZTP and push a custom config_db.json Port to older branches after #15685 is ported back - How I did it Re-introduce the logic to run the db_migrator on non-first boots - How to verify it Verified reboot and warm-reboot cases Signed-off-by: Vivek Reddy Karri <vkarri@nvidia.com> |
||
---|---|---|
.. | ||
per_namespace | ||
share_image | ||
arp_update_vars.j2 | ||
backend_acl.j2 | ||
buffers_config.j2 | ||
build_docker_cache.j2 | ||
cbf_config.j2 | ||
config-chassisdb.service.j2 | ||
config-setup.service.j2 | ||
database.service.j2 | ||
default_users.json.j2 | ||
dhcp_relay.service.j2 | ||
dns.j2 | ||
docker_image_ctl.j2 | ||
dockerd_regex.json | ||
eventd.service.j2 | ||
events_info.json | ||
iccpd.service.j2 | ||
init_cfg.json.j2 | ||
kernel_regex.json | ||
kube_cni.10-flannel.conflist | ||
lldp.service.j2 | ||
lldp.timer.j2 | ||
manifest.json.j2 | ||
mgmt-framework.service.j2 | ||
monit_regex.json | ||
mux.service.j2 | ||
nat.service.j2 | ||
organization_extensions.sh | ||
p4rt.service.j2 | ||
packages.json.j2 | ||
pde.service.j2 | ||
pmon.service.j2 | ||
qos_config.j2 | ||
radv.service.j2 | ||
restapi.service.j2 | ||
rsyslog_plugin.conf.j2 | ||
seu_regex.json | ||
sflow.service.j2 | ||
snmp.service.j2 | ||
sonic_debian_extension.j2 | ||
sonic_version.yml.j2 | ||
sonic.target | ||
sshd_regex.json | ||
swss_vars.j2 | ||
syncd_regex.json | ||
systemd_regex.json | ||
tacacs-config.service | ||
tacacs-config.timer | ||
telemetry.service.j2 | ||
updategraph.service.j2 |