qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gitlab/cirrus auth token failure


From: Thomas Huth
Subject: Re: gitlab/cirrus auth token failure
Date: Mon, 25 Oct 2021 14:39:36 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

On 25/10/2021 10.17, Daniel P. Berrangé wrote:
On Sun, Oct 24, 2021 at 06:15:38PM -0700, Richard Henderson wrote:
On 10/24/21 12:42 AM, Paolo Bonzini wrote:
On 22/10/21 20:31, Richard Henderson wrote:
Hi Daniel, you win the cookie because you committed cirrus.yml.

I should have reported this before the weekend, but at some point
this week the auth tokens expired(?).  All of the cirrus-run tests
are now failing:

cirrus_run.api.CirrusAPIError: API returned 1 error(s):
[ { 'extensions': {'classification': 'DataFetchingException'},
      'locations': [{'column': 13, 'line': 5}],
      'message': 'Exception while fetching data (/createBuild) : '
                 'AccessTokenAuthorization(token=[MASKED]) '
                 "doesn't have permissions to create builds for "
                 '5748266831446016!',
      'path': ['createBuild']}]

It seems to have fixed itself for kvm-unit-tests, so maybe it was just a
temporary issue within cirrus itself?

It's still failing today.

It fixed itself for libvirt too, but obviously qemu still seems to be
broken.

I'm wondering if it is as simple as having someone login to Cirrus CI
whose account owns the QEMU project. eg they might have disabled tokens
due to account inactivity.

If that doesn't work, then I'd suggest just re-creating the token.

FWIW, I recreated the tokens for my account last week when I saw it failing, and then it worked fine again, so recreating the tokens is likely one way to fix the issue.

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]