From: Chuck Lever <chuck.lever@oracle.com>
To: kdevops@lists.linux.dev
Subject: Debian unattended-upgrades
Date: Wed, 9 Apr 2025 15:54:22 -0400 [thread overview]
Message-ID: <7a5e28a4-38e7-4101-8bde-e99ec39c7a87@oracle.com> (raw)
Hi -
While testing with Debian 12 on AWS, I ran into this:
---
- name: Check if unattended-upgrades is installed
command: dpkg-query -W -f='${Status}' unattended-upgrades
register: unattended_upgrade_status
ignore_errors: true
changed_when: false
- name: Set fact if unattended-upgrades is installed
set_fact:
unattended_upgrades_installed: "{{ 'install ok installed' in
unattended_upgrade_status.stdout }}"
- name: Verify unattended-upgrades is not installed
fail:
msg: |
The unattended-upgrades package is installed on the base image, this
can cause tons of issues with CIs. Fix this by running the following
commands:
make cleancache
make bringup
when:
- unattended_upgrades_installed|bool
The Debian 12 image on AWS has the unattended-upgrades package
installed. I haven't checked Debian 11 or Debian on other cloud
providers.
- I did a "dpkg --purge unattended-upgrades" on each of the
instances, and this failure went away
- "make cleancache" might be appropriate for a libvirt installation,
but it definitely won't do anything for cloud; a fresh OS image
will always have that package (unless we make a custom image)
- Even so, if the libvirt OS image provider installs that package,
"make cleancache" won't eliminate the failure
Noting that later steps in
playbooks/roles/devconfig/tasks/install-deps/debian/main.yml disable and
uninstall unattended-upgrades anyway, what
is the purpose for the above logic? Can it be removed?
--
Chuck Lever
next reply other threads:[~2025-04-09 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 19:54 Chuck Lever [this message]
2025-04-09 20:16 ` Debian unattended-upgrades Chuck Lever
2025-04-10 8:29 ` Daniel Gomez
2025-04-10 13:49 ` Chuck Lever
2025-04-14 7:55 ` Daniel Gomez
2025-04-18 19:15 ` Luis Chamberlain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a5e28a4-38e7-4101-8bde-e99ec39c7a87@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kdevops@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox