Steps to replicate the issue (include links if applicable):
- Create job definitions in jobs.yaml
- Run toolforge jobs load jobs.yaml - observe jobs being created/updated
- Run toolforge jobs load jobs.yaml - observe jobs updated (though no changes are present)
What happens?:
Example job definitions:
tools.cluebotng@tools-bastion-13:~$ sha256sum jobs.yaml 0237c91a7e7b4208307256b9b8af519cb26e66226e27df968481813b2c2ec7b6 jobs.yaml tools.cluebotng@tools-bastion-13:~$ toolforge jobs load jobs.yaml INFO: loading job 'core'... Job core updated INFO: loading job 'bot'... Job bot updated INFO: loading job 'grafana-alloy'... Job grafana-alloy updated INFO: loading job 'irc-relay'... Job irc-relay updated INFO: loading job 'redis'... Job redis updated INFO: loading job 'report-review.import'... Job report-review.import updated INFO: loading job 'backup-database'... Job backup-database updated INFO: loading job 'prune-backups'... Job prune-backups updated INFO: 8 job(s) loaded successfully
Same exact config again:
tools.cluebotng@tools-bastion-13:~$ sha256sum jobs.yaml 0237c91a7e7b4208307256b9b8af519cb26e66226e27df968481813b2c2ec7b6 jobs.yaml tools.cluebotng@tools-bastion-13:~$ toolforge jobs load jobs.yaml INFO: loading job 'core'... Job core updated INFO: loading job 'bot'... Job bot updated INFO: loading job 'grafana-alloy'... Job grafana-alloy updated INFO: loading job 'irc-relay'... Job irc-relay updated INFO: loading job 'redis'... Job redis updated INFO: loading job 'report-review.import'... Job report-review.import updated INFO: loading job 'backup-database'... Job backup-database updated INFO: loading job 'prune-backups'... Job prune-backups updated INFO: 8 job(s) loaded successfully
What should have happened instead?:
Previously if there were no changes present for a job, then the job would not be updated (deleted/re-created), this behaviour should continue to exist today.
I also note that jobs load is very slow, taking > 1.5 min for 9 jobs.