waagent.log is not rotating 18.03.0-ce

[vesylapp]

Expected behavior

waagent.log will be rotated

Actual behavior

971.6M May 31 17:42 waagent.log

Information

• Full output of the diagnostics from "docker-diagnose" ran from one of the instance

swarm-manager000000:/var/log$ docker-diagnose OK hostname=swarm-manager000000 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS OK hostname=swarm-manager000001 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS OK hostname=swarm-manager000002 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS OK hostname=swarm-worker000000 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS OK hostname=swarm-worker000002 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS OK hostname=swarm-worker000003 session=1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS Done requesting diagnostics. Your diagnostics session ID is 1527788589-F2SPZSrZIqhsmvkKUQ9ZX9HJ9osFJXZS

[vesylapp]

More info:

It looks like waagent is relying on logrotate

The logrotate config files exist (as mentioned in #26) however it appears that logrotate is not actually installed on the VMs.

Also, @FrenchBen stated there that "Log size limited to 50m at the container level", but that does not appear to be the case - there is no size specified in waagent.logrotate as far as I can see:

           /var/log/waagent.log {
             compress
             monthly
             rotate 6
             notifempty
             missingok
           }

I think I also noticed that waagent in configured for verbose logging as well.