[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#926424: marked as done (cloud-init: No log rotation)

Your message dated Wed, 13 Mar 2024 02:49:13 +0000
with message-id <E1rkEg5-004fO2-I4@fasolo.debian.org>
and subject line Bug#926424: fixed in cloud-init 24.1.1-1
has caused the Debian Bug report #926424,
regarding cloud-init: No log rotation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
926424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926424
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cloud-init
Version: 18.3
Severity: wishlist
Tags: patch

Dear Maintainer,

The cloud-init system logs to the follow files:

 - /var/log/cloud-init-output.log
 - /var/log/cloud-init.log

There is nothing shipped which rotates these log files, which is a shame
as they'll grow everytime an instance is rebooted. We have some customers
with reasonably large log files now...

Please find attached a proposed logrotate file.

Cheers,
Andrew

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cloud-init depends on:
ii  cloud-guest-utils   0.29-1
ii  fdisk               2.33.1-0.1
ii  gdisk               1.0.3-1.1
ii  ifupdown            0.8.35
ii  locales             2.28-8
ii  lsb-base            10.2019031300
ii  lsb-release         10.2019031300
ii  net-tools           1.60+git20180626.aebd88e-1
ii  procps              2:3.3.15-2
ii  python3             3.7.3-1
pn  python3-configobj   <none>
ii  python3-jinja2      2.10-1
pn  python3-jsonpatch   <none>
pn  python3-jsonschema  <none>
pn  python3-oauthlib    <none>
ii  python3-requests    2.21.0-1
ii  python3-six         1.12.0-1
ii  python3-yaml        3.13-2
ii  util-linux          2.33.1-0.1

Versions of packages cloud-init recommends:
ii  eatmydata  105-7
ii  sudo       1.8.27-1

Versions of packages cloud-init suggests:
ii  btrfs-progs  4.20.2-1
ii  e2fsprogs    1.45.0-1
ii  xfsprogs     4.20.0-1

/var/log/cloud-init.log
/var/log/cloud-init-output.log
{
	weekly
	rotate 4
	compress
	delaycompress
	missingok
	notifempty
}

--- End Message ---
--- Begin Message --- 
Source: cloud-init
Source-Version: 24.1.1-1
Done: Noah Meyerhans <noahm@debian.org>

We believe that the bug you reported is fixed in the latest version of
cloud-init, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 926424@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Noah Meyerhans <noahm@debian.org> (supplier of updated cloud-init package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 11 Mar 2024 20:00:23 -0700
Source: cloud-init
Architecture: source
Version: 24.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team <debian-cloud@lists.debian.org>
Changed-By: Noah Meyerhans <noahm@debian.org>
Closes: 926424 955620 1025618 1057548
Changes:
 cloud-init (24.1.1-1) unstable; urgency=medium
 .
   [ Nick Brown ]
   * Add logrotate config (Closes: #926424)
 .
   [ Debian Janitor ]
   * Update lintian override info format in d/cloud-init.lintian-overrides
     on line 3-7.
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * Bump debhelper from old 10 to 13.
     + Drop check for DEB_BUILD_OPTIONS containing "nocheck", since
       debhelper now does this.
     + Replace --no-restart-on-upgrade with --no-stop-on-upgrade.
     + Use dh_installsystemd rather than deprecated dh_systemd_start.
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Repository-Browse.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Ross Vandegrift ]
   * d/control: Conflict with firewalld (Closes: #1025618)
     cloud-init and firewalld's systemd units jointly have startup cycles.
     Currently, they cannot be eliminated without breaking features of one
     or the other.
   * d/control: drop obsolete Depends on lsb-base
 .
   [ Noah Meyerhans ]
   * Fix debian/rules clean fails from git repo
     This may not be strictly correct from a pybuild perspective, but it
     avoids the need to call `setup.py` from the clean recipe.
     (Closes: #955620)
 .
   [ Ross Vandegrift ]
   * New upstream version 24.1 (Closes: #1057548)
   * d/p/0001-config-Support-APT-automated-mirror-selection.patch: refresh
   * d/p/0006-Disable-two-failing-WSL-unittests.patch: disable failing WSL tests
 .
   [ Noah Meyerhans ]
   * New upstream version 24.1.1
   * Drop patch 0006-Disable-two-failing-WSL-unittests.patch
Checksums-Sha1:
 8ffde165b91d09b26dd1a2539c4901cd22341c16 2440 cloud-init_24.1.1-1.dsc
 7e45254e6a7efd64a99a1abd2d6dee585f4069d4 1730335 cloud-init_24.1.1.orig.tar.gz
 0f42f704eeac76b3ed0485e683a3abd4691e2c84 26624 cloud-init_24.1.1-1.debian.tar.xz
 3461c15b85793e894a9fb5c770e1390100b3d9bd 7290 cloud-init_24.1.1-1_source.buildinfo
Checksums-Sha256:
 f54ecbc291bf6ecd05059628b11e78c5bc1990efb31e2fc2983d3aa9ad2bcf53 2440 cloud-init_24.1.1-1.dsc
 bda71fd0e4a2ad2c20941d941293a08bda490f075b24949b089f5425dcde1c73 1730335 cloud-init_24.1.1.orig.tar.gz
 3076753fd60c86b291e61a2878446315ced2b1f69247617c54cae24460075bb6 26624 cloud-init_24.1.1-1.debian.tar.xz
 82c8b70e0fba16bb01ebc776c071a2db65861c1c77ff7a66456d647cfe707428 7290 cloud-init_24.1.1-1_source.buildinfo
Files:
 f349eb943e4e51c060a42954eb547f84 2440 admin optional cloud-init_24.1.1-1.dsc
 46d30a80410623af3246d479e303949f 1730335 admin optional cloud-init_24.1.1.orig.tar.gz
 bd75e08032ea5aee3664e0dd54818ea3 26624 admin optional cloud-init_24.1.1-1.debian.tar.xz
 bfe3a344b2fd0cbb740d0cea01842414 7290 admin optional cloud-init_24.1.1-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmXxCA8RHG5vYWhtQGRl
Ymlhbi5vcmcACgkQ4+c1IpshdTVZHg/+JGRxaY/D8d+vPam5DyiChPwwkaNuyRky
exZxMot5yEhwNuq9Ek7pHBif5lqBHhtQrgBIJXudGLYx2EU/6X+y4orrT/yuZdyn
U98rZfE5SU+qdwWi0vpqv7IB/qHu5ZBdeK4ZGKzOcqkfr8IeOTXusx4TbDON1fPD
+z67h/+lnyMQHr4g01StujlxV5ySqv8aGKHTsQkSBFPPTfY69T/EvgelgzhjMx1M
ShkT6SqiIu6yx5G9Nt98J6FLTNixKUOYKfMCSBZ0utE8oWxvsn64J+kMT67vEjK5
PIjKdC0tBaGHuj9QC2AWfyI/E7rFgRK7ofMr23eli1/xt3N3FbIPzoBDe6FyEENC
OuSHopic70k/QJ8oUJxsTB4O7Lr96eJudYu77kI9bom1WAxguKEB82wmz/Polmtq
uwOaYjFbtNm5lq5N1lZAKyRQltWIwgePfC1WCQlW03qNowNrb6yZofyBwVAMcSKK
rXXRIaGaLlX9m59/PizdJD2z7pq95Hl/TnnPhbBqPIoeFA1buEEKKPDONtQPHUz7
Fwj5ZWuwv4B13VTCLLMA8Hmvg8E9nKADgdhL5oI/H+UCTgc9F8Q/LfKsgVXowyaG
KvbIM1jVCQvPtJIroHycUE5uktsLRVSxbf+lPR8IunltvkMeLnTCAuBCkDqfV3oS
ibc3IBbwi3U=
=pwDU
-----END PGP SIGNATURE-----

Attachment: pgpma3s6GSpa0.pgp
Description: PGP signature


--- End Message ---
Reply to: