Test-infra: Gubernator returns no matching index error

[nghialv]

What happened:
I have just deployed Gubernator on my GCP project but got the below internal error when access the test result.

Traceback (most recent call last):
  File "/base/alloc/tmpfs/dynamic_runtimes/python27g/f612b68945952bd1/python27/python27_lib/versions/third_party/webapp2-2.5.2/webapp2.py", line 1535, in __call__
    rv = self.handle_exception(request, response, e)

NeedIndexError: no matching index found.
The suggested index for this query is:
- kind: GHIssueDigest
  properties:
  - name: xref

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Please provide links to example occurrences, if any:

Anything else we need to know?:

[nghialv]

/area gubernator

[BenTheElder]

@Katharine (sorry! This is what happens when you're too helpful 😅)

On Wed, Jan 23, 2019, 18:23 Le Van Nghia <[email protected] wrote:

/area gubernator

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/10920#issuecomment-457042148,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4Bq3E7v3YUhFwIXFDfSrU8nksltnvBks5vGRkegaJpZM4aQAbX
.

[Katharine]

This is interesting.

My _guess_ is that this error is occurring because you have no GHIssueDigest entities stored (and never have). As such, Cloud Datastore's automatic simple index on properties doesn't exist, and consequently it chokes when trying to perform the lookup.

Do you have any GHIssueDigest entities? You can check at https://console.cloud.google.com/datastore/entities;kind=GHIssueDigest when the correct GCP project is active. They should start existing after gubernator receives a webhook from a GitHub issue.

[nghialv]

Hi, @Katharine
Thank for your quick reply.

Do you have any GHIssueDigest entities?

No, I don't have any GHIssueDigest entity.

I just want to use Gubernator to show the test results stored in GCS.
I don't need Gubernator's PR Dashboard at this time, so I didn't configure the GitHub webhook.
Can I have another way to make Gubernator work without integration with GitHub webhook?
(As I remember the previous version worked without GitHub webhook.)

Thank you.

[Katharine]

This lookup isn't actually for the PR dashboard, but instead for a feature that lists references to a given Gubernator page from github issues… as long as you're Kubernetes. It won't work anywhere else.

Gubernator is in maintenance mode (in favour of ultimate replacement by prow's Spyglass), but this is a fairly silly bug that we may as well fix.

/assign

[nghialv]

Thanks for your sharing.

I have just tried to use Spyglass and I have to say that I love it. Written in golang, easy to deploy, GKE instead of App Engine.
I will not close this issue because you added it to v1.14.

Thank you so much.

[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

[spiffxp]

/close
closing because spyglass works

[k8s-ci-robot]

@spiffxp: Closing this issue.

In response to this:

/close
closing because spyglass works

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.