[backport v2.10] [SURE-9460] Fleet not picking up gitrepo updates, no job created to update #3188
Description
This is a backport issue for #3138, automatically created via GitHub Actions workflow initiated by @manno
Original issue body:
SURE-9460
Issue description
After upgrading Rancher to 2.9.3 / fleet to v0.10.4, some gitrepos are no longer receiving updates. Customer update the repository, but changes are not pushed to the clusters. No Job is created to pull in the changes that should be tracked by the gitRepo.
In fleet v0.10.4, there were changes made to how jobs are managed in fleet. Could these changes be the cause of the issue here? #2932 seems to change how jobs are managed.
Business impact:
Unable to receive updates to applications using fleet for continuous delivery.
Troubleshooting steps:
GitJob pod, does not show that jobs are completing for those gitRepos, We are also unable to find jobs for the
Repro steps:
Upgrade to Rancher 2.9.3 from 2.9.2
Workaround:
Is a workaround available and implemented? yes
What is the workaround:
Customer found that by editing a gitRepo in the Rancher UI, changing nothing, then saving, it will eventually cause the repo to pull the change and make the necessary updates.
When making those changes, a couple lines are changed within the gitRepo:
spec.correctDrift: {} is added
status.commit is updated
status.lastPollingTriggered time is updated (time changed by more than a day).
Actual behavior:
repositories are not updated.
Expected behavior:
Repositories are updated.
Metadata
Metadata
Labels
Type
Projects
Status