September 2020 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2968) Maintaining Selenium Grid Infrastructure Research

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2968?page=com.atlassian.jir... ] Anton Marchukov commented on OVIRT-2968: ---------------------------------------- Closing since we found the way to use selenium on RHEL8 in Padman when we get rid of mock (in progress). > Maintaining Selenium Grid Infrastructure Research > ------------------------------------------------- > > Key: OVIRT-2968 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2968 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > During work on OST conversion it was found that we might benefit from > having selenium grid infrastructure [1] to be available as a general > service inside CI. This is basically by design. You can maintain selenium > grid and worker nodes and then expose it over network for general use. > Right now each OST run sets it up on its own each run. So I think having > dedicated and support infrastructure should be beneficial and could be part > of the infra. > Opening this ticket for research and discussion. > [1] https://www.selenium.dev/documentation/en/grid/ > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jir... ] Evgheni Dereveanchin updated OVIRT-3012: ---------------------------------------- Issue Type: Task (was: By-EMAIL) > Request for permission to run ovirt-system-tests_manual > ------------------------------------------------------- > > Key: OVIRT-3012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Pierre Lecomte > Assignee: infra > > Hello, > I have been told by Sandro I should be emailing this email to get access > rights to trigger manual OST jobs. > My login is plecomte on jenkins. > Thanks! > -- > Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jir... ] Evgheni Dereveanchin updated OVIRT-3012: ---------------------------------------- Resolution: Duplicate Status: Done (was: To Do) Closing duplicate > Request for permission to run ovirt-system-tests_manual > ------------------------------------------------------- > > Key: OVIRT-3012 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pierre Lecomte > Assignee: infra > > Hello, > I have been told by Sandro I should be emailing this email to get access > rights to trigger manual OST jobs. > My login is plecomte on jenkins. > Thanks! > -- > Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package

by Nir Soffer (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3011?page=com.atlassian.jir... ] Nir Soffer commented on OVIRT-3011: ----------------------------------- On Wed, Sep 9, 2020 at 10:41 AM Vojtech Juranek <vjuranek(a)redhat.com> wrote: > > Hi, > CI fails quite often with > > Error: Unable to find a match: python3-ioprocess-1.4.1 It was fixed in master and 4.3 today. The issue was an old requirement in automation for ioprocess-1.4.1. Eyal published 1.4.2 2 days ago, and for some reason 1.4.1 was removed from the repos, breaking the requirement. Since we have now copr repo, the builds are available few minutes after merging, there should not be any reason to add such requirements in automation. > > see e.g. [1, 2]. > Can someone please take a look? > Thanks > Vojta > > [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 > [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503____________... > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SYN66JCV4GP... > CI cannot find ioprocess package > -------------------------------- > > Key: OVIRT-3011 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3011 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Vojtech Juranek > Assignee: infra > Attachments: signature.asc > > > Hi, > CI fails quite often with > Error: Unable to find a match: python3-ioprocess-1.4.1 > see e.g. [1, 2]. > Can someone please take a look? > Thanks > Vojta > [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 > [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual

by Pierre Lecomte (oVirt JIRA)

Pierre Lecomte created OVIRT-3012: ------------------------------------- Summary: Request for permission to run ovirt-system-tests_manual Key: OVIRT-3012 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3012 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Pierre Lecomte Assignee: infra Hello, I have been told by Sandro I should be emailing this email to get access rights to trigger manual OST jobs. My login is plecomte on jenkins. Thanks! -- Pierre Lecomte | Virtualization Sustaining Engineering | Oracle -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package

by Vojtech Juranek (oVirt JIRA)

Vojtech Juranek created OVIRT-3011: -------------------------------------- Summary: CI cannot find ioprocess package Key: OVIRT-3011 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3011 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Vojtech Juranek Assignee: infra Hi, CI fails quite often with Error: Unable to find a match: python3-ioprocess-1.4.1 see e.g. [1, 2]. Can someone please take a look? Thanks Vojta [1] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23502 [2] https://jenkins.ovirt.org/job/vdsm_standard-check-patch/23503 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ Hey Nir, Yeah, we need to work on a better mechanism. I will create a ticket and discuss it in the infra meeting. Currently, the ovirt release master rpm is back, and soon the 4.3 + 4.2 will be restored. Thanks for the report! On Tue, Sep 8, 2020 at 2:42 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > On Tue, Sep 8, 2020 at 1:14 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > >> I found out the root cause was because of space issues in the nightly >> publisher run. >> >> The 3 ovirt publishers ran in together and the jenkins dir did not have >> that capacity. >> >> Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, >> > > Thanks! > > >> plus sent a patch [1] to ensure they will not run in parallel. >> >> [1]: https://gerrit.ovirt.org/111160 >> > > I probably don't understand the change, but it seems that all jobs > will run now at 00:00? > > I think we need to work on a better mechanism for updating the repository. > For example, we can have a symlink the to current repo: > > current -> 200908143754 > > 200908143754/ > repo files... > > 200908143830/ > repo files... > > When creating a new repo, create a new directory. Update the "current" > symlink only > if creating the new repo succeeded. Then delete the previous respo. > > With this the cases when the entire repo or some files are missing are not > possible. > > On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: >> >>> Hey, >>> >>> I am looking into this. >>> Will update with the results I will find. >>> >>> On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: >>> >>>> Hi Nir, >>>> >>>> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >>>> snapshot release RPM. >>>> >>>> I guess it's the same issue we had last time. >>>> >>>> Thanks in advance, >>>> >>>> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> >>>>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>>> > >>>>> > This is the second time, last time there was an issue during a >>>>> nightly job 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.rpm >>>>> 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 >>>>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>>>> > <html><head> >>>>> > <title>403 Forbidden</title> >>>>> > </head><body> >>>>> > <h1>Forbidden</h1> >>>>> > <p>You don't have permission to access >>>>> /pub/yum-repo/ovirt-release-master.rpm >>>>> > on this server.</p> >>>>> > </body></html> >>>>> > >>>>> > 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" >>>>> >>>>> >>>> >>>> -- >>>> >>>> Lev Veyde >>>> >>>> Senior Software Engineer, RHCE | RHCVA | MCITP >>>> >>>> Red Hat Israel >>>> >>>> <https://www.redhat.com> >>>> >>>> lev(a)redhat.com | lveyde(a)redhat.com >>>> <https://red.ht/sig> >>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>>> _______________________________________________ >>>> Devel mailing list -- devel(a)ovirt.org >>>> To unsubscribe send an email to devel-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/B7VMLC7JKYS... >>>> >>> > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > 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 > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > 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" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"

by Nir Soffer (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jir... ] Nir Soffer commented on OVIRT-3010: ----------------------------------- On Tue, Sep 8, 2020 at 1:14 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > I found out the root cause was because of space issues in the nightly > publisher run. > > The 3 ovirt publishers ran in together and the jenkins dir did not have > that capacity. > > Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, > Thanks! > plus sent a patch [1] to ensure they will not run in parallel. > > [1]: https://gerrit.ovirt.org/111160 > I probably don't understand the change, but it seems that all jobs will run now at 00:00? I think we need to work on a better mechanism for updating the repository. For example, we can have a symlink the to current repo: current -> 200908143754 200908143754/ repo files... 200908143830/ repo files... When creating a new repo, create a new directory. Update the "current" symlink only if creating the new repo succeeded. Then delete the previous respo. With this the cases when the entire repo or some files are missing are not possible. On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > >> Hey, >> >> I am looking into this. >> Will update with the results I will find. >> >> On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: >> >>> Hi Nir, >>> >>> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >>> snapshot release RPM. >>> >>> I guess it's the same issue we had last time. >>> >>> Thanks in advance, >>> >>> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >>> >>>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>>> > >>>> > This is the second time, last time there was an issue during a >>>> nightly job 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.rpm >>>> 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 >>>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>>> > <html><head> >>>> > <title>403 Forbidden</title> >>>> > </head><body> >>>> > <h1>Forbidden</h1> >>>> > <p>You don't have permission to access >>>> /pub/yum-repo/ovirt-release-master.rpm >>>> > on this server.</p> >>>> > </body></html> >>>> > >>>> > 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" >>>> >>>> >>> >>> -- >>> >>> Lev Veyde >>> >>> Senior Software Engineer, RHCE | RHCVA | MCITP >>> >>> Red Hat Israel >>> >>> <https://www.redhat.com> >>> >>> lev(a)redhat.com | lveyde(a)redhat.com >>> <https://red.ht/sig> >>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/B7VMLC7JKYS... >>> >> > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > 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 > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > 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" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ I found out the root cause was because of space issues in the nightly publisher run. The 3 ovirt publishers ran in together and the jenkins dir did not have that capacity. Currently, I am restoring the ovirt-master snapshot and then 4.3 + 4.2, plus sent a patch [1] to ensure they will not run in parallel. [1]: https://gerrit.ovirt.org/111160 On Tue, Sep 8, 2020 at 12:13 PM Ehud Yonasi <eyonasi(a)redhat.com> wrote: > Hey, > > I am looking into this. > Will update with the results I will find. > > On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: > >> Hi Nir, >> >> It looks like the CI job broke it again, breaking 4.2, 4.3 and master >> snapshot release RPM. >> >> I guess it's the same issue we had last time. >> >> Thanks in advance, >> >> On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >>> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >>> > >>> > This is the second time, last time there was an issue during a nightly >>> job 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.rpm >>> 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 >>> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >>> > <html><head> >>> > <title>403 Forbidden</title> >>> > </head><body> >>> > <h1>Forbidden</h1> >>> > <p>You don't have permission to access >>> /pub/yum-repo/ovirt-release-master.rpm >>> > on this server.</p> >>> > </body></html> >>> > >>> > 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" >>> >>> >> >> -- >> >> Lev Veyde >> >> Senior Software Engineer, RHCE | RHCVA | MCITP >> >> Red Hat Israel >> >> <https://www.redhat.com> >> >> lev(a)redhat.com | lveyde(a)redhat.com >> <https://red.ht/sig> >> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/B7VMLC7JKYS... >> > > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > 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 > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > 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" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

[JIRA] (OVIRT-3010) [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm"

by Ehud Yonasi (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jir... ] Ehud Yonasi commented on OVIRT-3010: ------------------------------------ Hey, I am looking into this. Will update with the results I will find. On Tue, Sep 8, 2020 at 12:00 PM Lev Veyde <lveyde(a)redhat.com> wrote: > Hi Nir, > > It looks like the CI job broke it again, breaking 4.2, 4.3 and master > snapshot release RPM. > > I guess it's the same issue we had last time. > > Thanks in advance, > > On Tue, Sep 8, 2020 at 11:45 AM Nir Soffer <nsoffer(a)redhat.com> wrote: > >> On Mon, Sep 7, 2020 at 2:30 PM Nir Soffer <nsoffer(a)redhat.com> wrote: >> > >> > This is the second time, last time there was an issue during a nightly >> job 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.rpm >> 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 >> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> >> > <html><head> >> > <title>403 Forbidden</title> >> > </head><body> >> > <h1>Forbidden</h1> >> > <p>You don't have permission to access >> /pub/yum-repo/ovirt-release-master.rpm >> > on this server.</p> >> > </body></html> >> > >> > 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" >> >> > > -- > > Lev Veyde > > Senior Software Engineer, RHCE | RHCVA | MCITP > > Red Hat Israel > > <https://www.redhat.com> > > lev(a)redhat.com | lveyde(a)redhat.com > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/B7VMLC7JKYS... > > [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > ------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-3010 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3010 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > This is the second time, last time there was an issue during a nightly job that > left the master snapshot repo broken. > 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 > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > <html><head> > <title>403 Forbidden</title> > </head><body> > <h1>Forbidden</h1> > <p>You don't have permission to access /pub/yum-repo/ovirt-release-master.rpm > on this server.</p> > </body></html> > 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" -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2020