dev scriptworkers sometimes run stale versions of images

I sometimes notice that a dev version of a scriptworker will encounter errors that are not possible if they are running the expected version of the code. Sure enough, doing an additional deployment (with no added code changes) will fix the issue, which leads me to believe that there are circumstances that can cause us to be running outdated versions of images.

I've never seen this in production, so I'm suspicious that there's something different between the two either here, in cloudops-infra, or perhaps even in k8s-autoscale.

I've noticed this a couple of times this week, and @gabrielBusta reports that he's seen it as well.

Inizia riproducendo il comportamento delle immagini obsolete in un deployment dev e confronta le versioni delle immagini prima e dopo un redeployment invariato. Esamina le differenze di deployment tra scriptworker-scripts, cloudops-infra e k8s-autoscale. Il lavoro è completato quando viene identificata la causa delle immagini obsolete e i deployment dev eseguono in modo coerente la versione di codice prevista.