You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
We suspect that the GitRepo drops out of the new polling. The new polling is based on RequeueAfter and uses the reconcilers workqueue.
We suspect this could happen, because of
a condition prevents the resource from being queued, when it should
resource drops out of requeue because of an unhandled error
not enough reconcile workers, so that some reconciles get delayed indefinitely
Until we can reproduce this:
We are adding some jitter to the polling, so that 300 gitrepos don't reconcile at the same time.
We shorten the resync period to pick up dropped gitrepos.
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.
The text was updated successfully, but these errors were encountered: