Hey, Apologies for a late response. On 11/28/22 08:39, Fabian Arrotin wrote: > On 28/11/2022 07:52, Anoop C S wrote: >> On Tue, 2022-09-13 at 11:22 +0200, Fabian Arrotin wrote: >> >> I would like to hear from other tenants for any objections around the >> above suggestion. Many of our jobs performing `dnf update` or `dnf >> install` started failing in a more frequent manner which feels bad >> looking at their respective statuses. >> >> If I don't get to hear any objections my recommendation would be to >> disable `dnf update` from cloud-init on EC2 instances. >> >> Thanks, >> Anoop C S. > > Hi, > > As nobody said anything about it, I just pushed the change to remove the "dnf update -y" part from the cloud-init configuration. In this case I agree with Anoop, even with the measures I have in place [0] I still occasionally bump into the original issue as well. So if it wasn't for Anoop, I'd start complaining sooner or later anyway :) > Ideally we'd let it there but if all tenants are starting themselves all their jobs with such dnf transaction, it's all good . Ideally we'd have refreshed centos 8s ami on regular basis and updating the ami id is just a git commit away for us (and Duffy then provisioning these new ones instead) That would be definitely ideal, but it looks like only C9S AMIs are updated regularly, not quite sure why it's not the case for C8S as well. [0] Calling `systemd-run --wait -p Wants=cloud-init.target -p After=cloud-init.target true` after getting a Duffy node -- Frantisek Sumsal GPG key ID: 0xFB738CE27B634E4B