[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gitlab-ci: amd64-opensuse-leap-container job failing
From: |
Daniel P . Berrangé |
Subject: |
Re: gitlab-ci: amd64-opensuse-leap-container job failing |
Date: |
Mon, 27 Sep 2021 15:57:48 +0100 |
User-agent: |
Mutt/2.0.7 (2021-05-04) |
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 :|