We noticed that some devices running old sonic releases could fill /var/log/ partition to 100%.
When /var/log partition is full, we noticed that some containers (if not all) would stay down after o.s. reboot.
The issue of filling /var/log partition has been solved in recent release (swss releases log file to allow logrotate to happen).
However, when we upgrade from old releases with full partitions to new releases, the storage space is not automatically freed. Therefore, human intervention is needed to clear these partitions.
As result, we would like to see that the upgrade process format the /var/log partition to mitigate the issue where a full /var/log partition could prevent rebooted device to start service.
We noticed that some devices running old sonic releases could fill /var/log/ partition to 100%.
When /var/log partition is full, we noticed that some containers (if not all) would stay down after o.s. reboot.
The issue of filling /var/log partition has been solved in recent release (swss releases log file to allow logrotate to happen).
However, when we upgrade from old releases with full partitions to new releases, the storage space is not automatically freed. Therefore, human intervention is needed to clear these partitions.
As result, we would like to see that the upgrade process format the /var/log partition to mitigate the issue where a full /var/log partition could prevent rebooted device to start service.