qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab/cirrus auth token failure
Date: Mon, 25 Oct 2021 09:17:08 +0100	[thread overview]
Message-ID: <YXZoBDndaM5nCpwU@redhat.com> (raw)
In-Reply-To: <c713ff41-0546-ee6c-dafa-f83624437fc2@linaro.org>

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.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-10-25  8:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22 18:31 gitlab/cirrus auth token failure Richard Henderson
2021-10-24  7:42 ` Paolo Bonzini
2021-10-25  1:15   ` Richard Henderson
2021-10-25  8:17     ` Daniel P. Berrangé [this message]
2021-10-25 12:39       ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YXZoBDndaM5nCpwU@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).