prow fails to mark periodic as completed and run new runs even though the results page shows the job passed

[BenTheElder]

https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-conformance-kind-ga-only/1858905568668815360

Not sure what happened here, but if I go to:
https://prow.k8s.io/?job=ci-kubernetes-conformance-kind-ga-only

There's a single job, that is state "Pending" (??) and yet if I click the logs link it is the link above with the completed job...

@petr-muller any ideas here?

/kind bug

[BenTheElder]

... I think the prowjob CR got GCed, which is also breaking the ability to click "rerun" to trigger it again, so we have a periodic job pretty much totally stuck.

[BenTheElder]

This seems to have worked itself out, not sure what happened. It is marked as passing now.

https://prow.k8s.io/?job=ci-kubernetes-conformance-kind-ga-only

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale