September 2020 - Infra - oVirt List Archives

[JIRA] (OVIRT-2968) Maintaining Selenium Grid Infrastructure Research
by Anton Marchukov (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2968?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Evgheni Dereveanchin (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Evgheni Dereveanchin (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3012?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package
by Nir Soffer (oVirt JIRA) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3011?page=com.atlassian.jira.… ] 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/SYN66JCV4GPYS… > 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)

1 0

[JIRA] (OVIRT-3012) Request for permission to run ovirt-system-tests_manual
by Pierre Lecomte (oVirt JIRA) 10 Sep '20

10 Sep '20

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)

1 0

[JIRA] (OVIRT-3011) CI cannot find ioprocess package
by Vojtech Juranek (oVirt JIRA) 10 Sep '20

10 Sep '20

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)

1 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) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] 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/B7VMLC7JKYSU2… >>>> >>> > [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)

1 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) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] 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/B7VMLC7JKYSU2… >>> >> > [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)

1 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) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] 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/B7VMLC7JKYSU2… >> > > [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)

1 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) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] 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/B7VMLC7JKYSU2… > > [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)

1 0

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

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Lev Veyde commented on OVIRT-3010: ---------------------------------- 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> > [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)

1 0

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

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-3010: ---------------------------------------- > Begin forwarded message: > > From: Nir Soffer <nsoffer(a)redhat.com> > Subject: Re: [CI] Builds broken by "Status code: 403 for http://resources.ovirt.org/pub/yum-repo/ovirt-release-master.rpm" > Date: 8 September 2020 at 10:44:44 CEST > To: infra-support(a)ovirt.org > Cc: devel <devel(a)ovirt.org>, Lev Veyde <lveyde(a)redhat.com>, Anton Marchukov <amarchuk(a)redhat.com>, "Nisan, Tal" <tnisan(a)redhat.com>, Galit Rosenthal <grosenth(a)redhat.com>, Michal Skrivanek <mskrivan(a)redhat.com>, infra <infra(a)ovirt.org> > > 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" > -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat > [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)

1 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) 10 Sep '20

10 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-3010?page=com.atlassian.jira.… ] Nir Soffer commented on OVIRT-3010: ----------------------------------- 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" > [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)

1 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) 10 Sep '20

10 Sep '20

Nir Soffer created OVIRT-3010: --------------------------------- Summary: [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)

1 0

[JIRA] (OVIRT-3009) errors on infra
by Yedidyah Bar David (oVirt JIRA) 10 Sep '20

10 Sep '20

Yedidyah Bar David created OVIRT-3009: ----------------------------------------- Summary: errors on infra Key: OVIRT-3009 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3009 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi, 1. Please see thread "[ovirt-devel] gerrit pull/clone timeout". 2. Please see [1] - it failed check-merged, I tried again, and it failed again. In both cases, e.g. [2]: Error: Error downloading packages: Cannot download x86_64/ovirt-engine-wildfly-19.1.0-2.el8.x86_64.rpm: All mirrors were tried Of course, I can't be sure these are due to a single root cause. Please fix :-) Thanks, [1] https://gerrit.ovirt.org/111098 [2] https://jenkins.ovirt.org/job/ovirt-dwh_standard-on-merge/124/artifact/buil… -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-3008) IMAPS certificate expired on lists.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 10 Sep '20

10 Sep '20

Evgheni Dereveanchin created OVIRT-3008: ------------------------------------------- Summary: IMAPS certificate expired on lists.ovirt.org Key: OVIRT-3008 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3008 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra We've got reports about ticket creation issues from email. Looking at dovecot logs the email handler tries to connect but disconnects immediately. Connecting to port 993 shows an expired cert: openssl s_client lists.ovirt.org:993 CONNECTED(00000003) depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 verify return:1 depth=0 CN = lists.ovirt.org verify error:num=10:certificate has expired notAfter=Jul 1 09:47:58 2020 GMT verify return:1 depth=0 CN = lists.ovirt.org notAfter=Jul 1 09:47:58 2020 GMT verify return:1 --- Certificate chain 0 s:CN = lists.ovirt.org i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 1 s:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 i:O = Digital Signature Trust Co., CN = DST Root CA X3 Looks like dovecot is not getting restarted after a new cert is issued. Leaving as-is for now for further review. A service restart should theoretically be enough to make use of the current cert. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 363 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Sep '20

10 Sep '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 363 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #363 [Martin Necas] Ansible: remove nic_on_boot from cloud-init ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.100_basic_ui_sanity_pytest.test_login[firefox] Error Message: test setup failure Stack Trace: engine_fqdn = 'engine', engine_ip = '192.168.201.4' @pytest.fixture(scope="session") def hub_url(engine_fqdn, engine_ip): env_url = _env_hub_url() if env_url is not None: yield env_url else: backend = _grid_backend() if backend == "podman": if os_utils.on_centos(8) and os_utils.inside_mock(): pytest.skip("podman doesn't work in mock") hub_port = network_utils.find_free_port(4444, 4544) with podman.grid(engine_fqdn, engine_ip, hub_port=hub_port) as hub_url: yield hub_url elif backend == "docker": > with docker.grid(engine_fqdn, engine_ip) as hub_url: ../ost_utils/ost_utils/pytest/fixtures/selenium/__init__.py:76: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ /usr/lib64/python2.7/contextlib.py:17: in __enter__ return self.gen.next() ../ost_utils/ost_utils/selenium/docker.py:118: in grid with _network(network_name): /usr/lib64/python2.7/contextlib.py:17: in __enter__ return self.gen.next() ../ost_utils/ost_utils/selenium/docker.py:61: in _network shell(["docker", "network", "create", network_name]) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ args = ['docker', 'network', 'create', 'grid'], bytes_output = False kwargs = {}, process = <subprocess.Popen object at 0x7f48c8c633d0>, out = '' err = 'Error response from daemon: network with name grid already exists ' def shell(args, bytes_output=False, **kwargs): process = subprocess.Popen(args, stdout=subprocess.PIPE, stderr=subprocess.PIPE, **kwargs) out, err = process.communicate() if not bytes_output: out = out.decode("utf-8") err = err.decode("utf-8") if process.returncode: > raise ShellError(process.returncode, out, err) E ShellError: Command failed with rc=1. Stdout: E E Stderr: E Error response from daemon: network with name grid already exists ../ost_utils/ost_utils/shell.py:51: ShellError

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 361 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Sep '20

10 Sep '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 361 Build Status: Failure Triggered By: Started by user Parth Dhanjal ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #361 No changes ----------------- Failed Tests: ----------------- No tests ran.

1 1

oVirt infra daily report - unstable production jobs - 1309
by jenkins＠jenkins.phx.ovirt.org 10 Sep '20

10 Sep '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1309//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-3007) permission to run ovirt-system-tests_manual
by Pierre Lecomte (oVirt JIRA) 09 Sep '20

09 Sep '20

Pierre Lecomte created OVIRT-3007: ------------------------------------- Summary: permission to run ovirt-system-tests_manual Key: OVIRT-3007 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3007 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Components: OST Manual job Reporter: Pierre Lecomte Assignee: infra I emailed infra-support(a)ovirt.org but this does not appear to have created the ticket here. -------- Forwarded Message -------- Subject: Request for permission to run ovirt-system-tests_manual Date: Wed, 9 Sep 2020 18:04:08 +0200 From: Pierre Lecomte <pierre.lecomte(a)oracle.com> To: infra-support(a)ovirt.org 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. (Note : There appears to be a pierre.lecomte(a)oracle.com login on the Jenkins host but I did not create it- It's maybe tied with my login on the gerrit instance which is achieved using github credentials). Thanks! -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-2847) Certain substage fails continously with missing useradd in chroot
by Evgheni Dereveanchin (oVirt JIRA) 09 Sep '20

09 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2847?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2847: ---------------------------------------- Issue Type: Bug (was: By-EMAIL) > Certain substage fails continously with missing useradd in chroot > ----------------------------------------------------------------- > > Key: OVIRT-2847 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2847 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Bell Levin > Assignee: infra > > Hello! > I have had a contentious error in a certain job. > The error seems to be: > ERROR: Could not find useradd in chroot, maybe the install failed? > you can see it in the logs here: > https://jenkins.ovirt.org/job/standard-manual-runner/983/artifact/check-net… > In the check-network.functional-ovs-switch-lib job, in the following runs: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Please advice. > Thanks, > Bell -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[JIRA] (OVIRT-2847) Certain substage fails continously with missing useradd in chroot
by Evgheni Dereveanchin (oVirt JIRA) 09 Sep '20

09 Sep '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2847?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2847: ---------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) This seems like an old issue with Fedora mocks. Closing since I've not seen this issue in a while > Certain substage fails continously with missing useradd in chroot > ----------------------------------------------------------------- > > Key: OVIRT-2847 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2847 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Bell Levin > Assignee: infra > > Hello! > I have had a contentious error in a certain job. > The error seems to be: > ERROR: Could not find useradd in chroot, maybe the install failed? > you can see it in the logs here: > https://jenkins.ovirt.org/job/standard-manual-runner/983/artifact/check-net… > In the check-network.functional-ovs-switch-lib job, in the following runs: > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner… > Please advice. > Thanks, > Bell -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100145)

1 0

[oVirt Jenkins] ovirt-system-tests_basic-suite-master_nightly - Build # 359 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 Sep '20

09 Sep '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-master_nightly… Build Number: 359 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #359 [Marcin Sobczyk] basic: Drop outdated code ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: basic-suite-master.test-scenarios.098_ovirt_provider_ovn_pytest.test_use_ovn_provider Error Message: Error: Fault reason is "Operation Failed". Fault detail is "[Cannot add Network. The name of the logical network 'network_1' is already used by an existing logical network in the same data-center. -Please choose a different name.]". HTTP response code is 409. Stack Trace: prefix = <ovirtlago.prefix.OvirtPrefix object at 0x7f8782aba190> api_v4 = <ovirtsdk4.Connection object at 0x7f8781fee590> @versioning.require_version(4, 2) def test_use_ovn_provider(prefix, api_v4): engine = api_v4.system_service() engine_ip = prefix.virt_env.engine_vm().ip() provider_id = network_utils_v4.get_default_ovn_provider_id(engine) token_id = _get_auth_token(engine_ip) _validate_db_empty(token_id, engine_ip) with _disable_auto_sync(api_v4, provider_id): network1_id = _add_network( token_id, engine_ip, NETWORK_1, ) subnet1_id = _add_subnet( token_id, engine_ip, SUBNET_1, network1_id, ) port1_id = _add_port( token_id, engine_ip, PORT_1, network1_id, ) _validate_network(token_id, engine_ip, NETWORK_1, network1_id) _validate_port(token_id, engine_ip, PORT_1, port1_id, network1_id) _validate_subnet(token_id, engine_ip, SUBNET_1, subnet1_id, network1_id) datacenter_id = _get_datacenter_id(api_v4) > _import_network_to_ovirt(api_v4, provider_id, network1_id, datacenter_id) ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:474: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ ../basic-suite-master/test-scenarios/098_ovirt_provider_ovn_pytest.py:364: in _import_network_to_ovirt id=datacenter_id /usr/lib64/python2.7/site-packages/ovirtsdk4/services.py:18492: in import_ return self._internal_action(action, 'import', None, headers, query, wait) /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:299: in _internal_action return future.wait() if wait else future /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:55: in wait return self._code(response) /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:296: in callback self._check_fault(response) /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:134: in _check_fault self._raise_error(response, body.fault) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ response = <ovirtsdk4.http.Response object at 0x7f8781fee450> detail = <ovirtsdk4.types.Fault object at 0x7f8781fee690> @staticmethod def _raise_error(response, detail=None): """ Creates and raises an error containing the details of the given HTTP response and fault. This method is intended for internal use by other components of the SDK. Refrain from using it directly, as backwards compatibility isn't guaranteed. """ fault = detail if isinstance(detail, types.Fault) else None msg = '' if fault: if fault.reason: if msg: msg += ' ' msg = msg + 'Fault reason is "%s".' % fault.reason if fault.detail: if msg: msg += ' ' msg = msg + 'Fault detail is "%s".' % fault.detail if response: if response.code: if msg: msg += ' ' msg = msg + 'HTTP response code is %s.' % response.code if response.message: if msg: msg += ' ' msg = msg + 'HTTP response message is "%s".' % response.message if isinstance(detail, six.string_types): if msg: msg += ' ' msg = msg + detail + '.' class_ = Error if response is not None: if response.code in [401, 403]: class_ = AuthError elif response.code == 404: class_ = NotFoundError error = class_(msg) error.code = response.code if response else None error.fault = fault > raise error E Error: Fault reason is "Operation Failed". Fault detail is "[Cannot add Network. The name of the logical network 'network_1' is already used by an existing logical network in the same data-center. E -Please choose a different name.]". HTTP response code is 409. /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:118: Error

1 1

[oVirt Jenkins] ovirt-system-tests_basic-suite-4.3_nightly - Build # 355 - Failure!
by jenkins＠jenkins.phx.ovirt.org 09 Sep '20

09 Sep '20

Project: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/ Build: https://jenkins.ovirt.org/job/ovirt-system-tests_basic-suite-4.3_nightly/35… Build Number: 355 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #355 [Marcin Sobczyk] ost_utils: network_utils: Add 'get_ips[6]' functions ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 005_network_by_label.assign_labeled_network Error Message: False != True after 180 seconds Stack Trace: Traceback (most recent call last): File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper return func(get_test_prefix(), *args, **kwargs) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 79, in wrapper prefix.virt_env.engine_vm().get_api(api_ver=4), *args, **kwargs File "/home/jenkins/agent/workspace/ovirt-system-tests_basic-suite-4.3_nightly/ovirt-system-tests/basic-suite-4.3/test-scenarios/005_network_by_label.py", line 149, in assign_labeled_network host_service, LABELED_NET_NAME)) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 282, in assert_true_within_short assert_equals_within_short(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 266, in assert_equals_within_short func, value, SHORT_TIMEOUT, allowed_exceptions=allowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 252, in assert_equals_within '%s != %s after %s seconds' % (res, value, timeout) AssertionError: False != True after 180 seconds

1 1

oVirt infra daily report - unstable production jobs - 1308
by jenkins＠jenkins.phx.ovirt.org 09 Sep '20

09 Sep '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1308//artifact/exported… Cheers, Jenkins

1 0