Ubuntu
unattended-upgrades package

unattended-upgrades conflicts with kubernetes gracefullshutdown

Bug #1949241 reported by Piotr Maksymiuk
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unattended-upgrades (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Kubernetes 1.22 brings GracefullNodeShutdown into beta, by leveraging systemd-inhibit. It tries to detect the current InhibitDelayMaxSec, and if it's less than the requested, will place a 99-kubelet.conf in /etc/systemd/logind.conf.d

However, this doesn't work as systemd-analyze cat-config systemd/logind.conf would show that /usr/lib/systemd/logind.conf.d/unattended-upgrades-logind-maxdelay.conf comes last, and overwrites any requested maxium down to 30 seconds.

This file should either be customizable, or renamed to something like 10-unattended-upgrades-logind-maxdelay.conf so that it would be evaluated earlier

This is on a cloud image of Ubuntu 21.10

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unattended-upgrades (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.