From nsoffer at redhat.com Tue Sep 8 08:45:16 2020 Content-Type: multipart/mixed; boundary="===============8712923187467490134==" MIME-Version: 1.0 From: Nir Soffer To: devel at ovirt.org Subject: [ovirt-devel] Re: [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" Date: Tue, 08 Sep 2020 11:44:44 +0300 Message-ID: In-Reply-To: CAMRbyys0EFmxrrUhVFOH705tWEnG5=CBZwFx6SQeH0G6RzUxkw@mail.gmail.com --===============8712923187467490134== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer wrote: > > This is the second time, last time there was an issue during a nightly jo= b that > left the master snapshot repo broken. This is still broken today. In the past sending mail to infra-support created a bug, and someone was handling issue quickly. This seems to be broken now. We depend on http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.r= pm for development and CI. When the rpm is missing, CI jobs fail, and developers cannot update their setup. Please fix it as soon as possible. > I have 3 failure builds: > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7744/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7751/ > https://jenkins.ovirt.org/job/ovirt-engine_standard-check-patch/7755/ > > All seems to fail in: > > [2020-09-07T10:00:56.163Z] + dnf install -y > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > [2020-09-07T10:01:08.524Z] Status code: 403 for > http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm (IP: > 66.187.230.40) > > Checking manually show: > > $ curl https://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm > > > 403 Forbidden > >

Forbidden

>

You don't have permission to access /pub/yum-repo/ovirt-release-master= .rpm > on this server.

> > > Looking at: > https://resources.ovirt.org/pub/yum-repo/ > > ovirt-elease-master.rpm does not exist. > > So we have 2 issues: > - The file does not exist > - We return "403 Forbidden" instead of "404 Not Found" --===============8712923187467490134==--