mozilla-releng / mozilla-releng/scriptworker-scripts
dev scriptworkers sometimes run stale versions of images
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 38
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 14
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the stale-image behavior in a dev deployment and compare the image versions before and after an unchanged redeployment. Inspect the deployment differences across scriptworker-scripts, cloudops-infra, and k8s-autoscale. Done means the cause of outdated images is identified and dev deployments consistently run the expected code version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100