Renamed repo breaks lighthouse normal function

[apenen]

Hi!

When someone renames a project in git (badly done)... The current PR job has to be deleted or jx cannot continue with the next.

{"component":"keeper","error":"failed to perform REST query for PRs: listing all open pull requests for : 404 Project Not Found","file":"/workspace/source/cmd/keeper/main.go:182","func":"main.sync","level":"error","msg":"Error syncing.","time":"2020-10-16T06:48:28Z"}

Any ideas?

[jenkins-x-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.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

[keskad]

Hi, I have exactly the same issue. I think its pretty critical in my opinion, here is the use case:

• Non-administrative user deletes or renames his/her own repository from Gitlab/Github
• Then lighthouse-keeper does not work for ANY project on Jenkins X and nobody knows why

Here are logs (using Gitlab self hosted):

{"component":"keeper","controller":"sync","error":"listing all open pull requests for root/golang-http-test: Not Found","file":"/workspace/source/pkg/keeper/keeper.go:336","func":"github.com/jenkins-x/lighthouse/pkg/keeper.(*DefaultController).Sync","level":"warning","msg":"failed to perform REST query for PRs","time":"2022-01-31T11:41:16Z"}

In my opinion non-administrative user should not be able to impact on other user's work.

Using ghcr.io/jenkins-x/lighthouse-keeper:1.5.7

[keskad]

/remove-lifecycle rotten