From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Thomas Huth <thuth@redhat.com>, "Cho, Yu-Chen" <acho@suse.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: gitlab-ci: amd64-opensuse-leap-container job failing
Date: Mon, 27 Sep 2021 15:57:48 +0100 [thread overview]
Message-ID: <YVHb7E0u+gYTjwWW@redhat.com> (raw)
In-Reply-To: <89b3ce1b-5eea-a3e2-8361-493a8a96d6a2@amsat.org>
On Mon, Sep 27, 2021 at 04:35:04PM +0200, Philippe Mathieu-Daudé wrote:
> On 9/27/21 15:47, Daniel P. Berrangé wrote:
> > On Mon, Sep 27, 2021 at 09:35:22AM +0100, Daniel P. Berrangé wrote:
> >> On Sun, Sep 26, 2021 at 07:23:56PM +0200, Philippe Mathieu-Daudé wrote:
> >>> Hi,
> >>>
> >>> FYI the OpenSUSE job is failing since few days, i.e.:
> >>> https://gitlab.com/qemu-project/qemu/-/jobs/1622345026
> >>>
> >>> Retrieving repository 'Main Repository' metadata
> >>> [..........................................................error]
> >>> Repository 'Main Repository' is invalid.
> >>>
> >>> [repo-oss|http://download.opensuse.org/distribution/leap/15.2/repo/oss/]
> >>> Valid metadata not found at specified URL
> >>> History:
> >>> - Download (curl) error for
> >>> 'http://download.opensuse.org/distribution/leap/15.2/repo/oss/repodata/repomd.xml':
> >>> Error code: Curl error 56
> >>> Error message: Recv failure: Connection reset by peer
> >>> - Can't provide /repodata/repomd.xml
> >>> Please check if the URIs defined for this repository are pointing to a
> >>> valid repository.
> >>> Warning: Skipping repository 'Main Repository' because of the above error.
> >>>
> >>> I tried to run 'zypper ref' with:
> >>
> >> It isn't confined to only SuSE. In libvirt we've had similar problems
> >> with several other jobs, though are suse jobs are the worst affected.
> >>
> >> GitLab have finally acknowledged it is an general infra issue affecting
> >> many things:
> >>
> >> https://status.gitlab.com/
> >> https://gitlab.com/gitlab-com/gl-infra/production/-/issues/5590
> >
> > Setting GitLab CI env var works around the problem temporarily:
> >
> > FF_NETWORK_PER_BUILD=true
>
> Do you know if we need to recreate the pipeline?
> (It didn't work on already failing one, I'm going to test
> a freshly created one now).
You shoudln't need to re-create the pipeline, just retry the job.
If setting the variable in the web UI, make sure "Protect variable"
is *not* set. Only the "master" branch is protected by default
so other branches won't get protected variables set in their jobs.
>
> > You can set it for all repos under a group eg
> >
> > https://gitlab.com/groups/qemu-project/-/settings/ci_cd
> >
> > or per repo eg
> >
> > https://gitlab.com/berrange/libvirt/-/settings/ci_cd
> >
> >
> > Regards,
> > Daniel
> >
>
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 :|
next prev parent reply other threads:[~2021-09-27 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 17:23 gitlab-ci: amd64-opensuse-leap-container job failing Philippe Mathieu-Daudé
2021-09-27 8:35 ` Daniel P. Berrangé
2021-09-27 9:44 ` Al Cho
2021-09-27 9:49 ` Philippe Mathieu-Daudé
2021-09-27 13:47 ` Daniel P. Berrangé
2021-09-27 14:35 ` Philippe Mathieu-Daudé
2021-09-27 14:57 ` Daniel P. Berrangé [this message]
2021-09-29 16:57 ` Daniel P. Berrangé
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=YVHb7E0u+gYTjwWW@redhat.com \
--to=berrange@redhat.com \
--cc=acho@suse.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.