Comment 3 for bug 1981960

Aleksandra (algol30) generally cloud-init should not be emitting debug logs with a frequency that impacts your system in "one-two days". This points to something unexpected in the environment that logs would help us better understand. Ultimately, we want to understand what types of potentially repeated events seem to be saturating your logs.

  We may be able to get to that understanding a bit with some of the following:

  1. cloud-init --version
  2. cloud-nit status --long
  3. Are there repeated logs/tracebacks that seem to keep happening on the system (a bunch of failed retries/hotplug being enabled?
  4. cloud-init analyze show (Tells us how many boot events cloud-init has gone through on the system
  5. sudo cloud-init query --all (Note you will have to manually look through this JSON output specifically under the keys "ds" "merged_cfg" "vendordata", "userdata" to make sure you can change any securiry sensitive fields or passwords to REDACTED.