You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue or Feature Request:
When testing locally in aws-dev, I issued an apiclient reboot command and hit an error where this pair of messages spammed the console during system shutdown:
[ 135.289329] host-containers@admin[1168]: [email protected] has no holdoff time, scheduling restart.
[ 135.290142] host-containers@admin[1168]: Stop job pending for unit, delaying automatic restart.
I've also heard scattered reports that enabling the admin container can cause delays when scaling in a cluster, and I suspect this might be the culprit.
systemd fixed this upstream in systemd/systemd@c972880 which we should add to the systemd patches here.
The text was updated successfully, but these errors were encountered:
Image I'm using:
v0.11.7
Issue or Feature Request:
When testing locally in
aws-dev
, I issued anapiclient reboot
command and hit an error where this pair of messages spammed the console during system shutdown:I've also heard scattered reports that enabling the admin container can cause delays when scaling in a cluster, and I suspect this might be the culprit.
systemd fixed this upstream in systemd/systemd@c972880 which we should add to the systemd patches here.
The text was updated successfully, but these errors were encountered: