Requeue the snapshot object

[xing-yang]

This was brought up during the code review by
@msau42 in #211.

Looking at the caller, I see that we don't requeue the object and instead rely on resync period to retry. I think we should change the behavior to requeue, but we should also make sure the workqueue has proper throttling/backoff as well.

Open this issue to track it. I'll look at this after v2.0 release.

[xing-yang]

/assign @xing-yang

[xing-yang]

There's a question raised in issue #225 that we should do retry immediately after update content status fails. We should re-visit it when we look at this requeue issue.

[xing-yang]

Also for successfully processed snapshot, we should "Forget" it so it won't be queued until another change happens.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[xing-yang]

/remove-lifecycle stale

[humblec]

@xing-yang cant we close this in favor of #225 . Basically retry on update fail and forgetting the requeue once its successful should address this issue as well, Isnt it ? or anything else I missed ?

[xing-yang]

Let's keep this one open until that PR is merged.

[humblec]

Let's keep this one open until that PR is merged.

ok.. then lets wait. do we need to add this PR as well in fix section of the PR ?

[xing-yang]

This is fixed.