- Infra - oVirt List Archives

[JIRA] (OVIRT-1424) Re: Build timed out in Vdsm check-merged (was: False OST failure)
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1424?page=com.atlassian.jira.… ] eedri updated OVIRT-1424: ------------------------- Epic Link: OVIRT-400 > Re: Build timed out in Vdsm check-merged (was: False OST failure) > ----------------------------------------------------------------- > > Key: OVIRT-1424 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1424 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > adding infra-support to open a ticket. > On Thu, Jun 1, 2017 at 10:28 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/1870/ > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] eedri updated OVIRT-1427: ------------------------- Epic Link: OVIRT-400 > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1427) Dependencies between ovirt-engine and vdsm-jsonrpc-java
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1427?page=com.atlassian.jira.… ] eedri updated OVIRT-1427: ------------------------- Epic Link: OVIRT-400 > Dependencies between ovirt-engine and vdsm-jsonrpc-java > ------------------------------------------------------- > > Key: OVIRT-1427 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1427 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: infra > > Recently we had and issue that newer version of vdsm-jsonrpc-java was > available but engine spec was not updated yet. Engine patch contained spec > and module.xml changes which provided dependencies required by new version > of jsonrpc. CI used the new version of jsonrpc without engine patch being > merged which caused several issues. > This ticket is open to track how we could mitigate similar issues in the > future. > Thanks, > Piotr -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1431) Need a test projet in gerrit-staging
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1431?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1431: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Need a test projet in gerrit-staging > ------------------------------------ > > Key: OVIRT-1431 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1431 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan(a)redhat.com > Assignee: Evgheni Dereveanchin > > Hi, > Please create a test project under gerrit-staging and make me the admin in > order to test changes in gerrit reviewer plugin. > Thanks -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1434) Re: Every user can abandon patches that are not his
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1434?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1434: ---------------------------- Assignee: Shlomo Ben David (was: infra) is this done? > Re: Every user can abandon patches that are not his > --------------------------------------------------- > > Key: OVIRT-1434 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1434 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: Shlomo Ben David > > Adding infra support to open a ticket. > On Wed, Jun 7, 2017 at 3:11 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Hi, > > I've discovered that every user can abandon patches even if they are not > > his, here's an example of Shani abandoning my patch which shouldn't be > > allowed: > > > > https://gerrit.ovirt.org/#/c/77919/ > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1441) [RFE] Add a jenkins job for copying external packages to static repos
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1441?page=com.atlassian.jira.… ] eedri updated OVIRT-1441: ------------------------- Resolution: Won't Do Status: Done (was: To Do) As stated in the last comments, we shouldn't allow any new packages to be deployed to static repos. on the contrary, we have a ticket already to have them cleaned as they created multiple issues in the past and caused OST and other jobs to fail. the supported flows are mentioned in this ticket, it should either be external repo or internal oVirt package, which has a build-artifacts jobs. if there is a need to use a package that doesn't comply to any of the above, please open a ticket and explain the need and why it can't be done in the supported flows. > [RFE] Add a jenkins job for copying external packages to static repos > --------------------------------------------------------------------- > > Key: OVIRT-1441 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1441 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Description of problem: > Currently, when we want to copy a package from elsewhere to > resources.ovirt.org, we manually run repoman. It will be nice to have > a jenkins job for this - with inputs probably being URLs of source > packages/repos and target versions to copy to: > 1. It will not require us anymore to login there and do sensitive > stuff on it directly > 2. It will have proper logs, allowing much more easily understand when > a package was added, by whom, and even perhaps why. So better add to > the inputs also 'Notes'. > This is cloned from: > https://bugzilla.redhat.com/show_bug.cgi?id=1455316 > Best, > -- > Didi -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1442) Re: Build timed out in Vdsm check-merged
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1442?page=com.atlassian.jira.… ] eedri updated OVIRT-1442: ------------------------- Epic Link: OVIRT-400 > Re: Build timed out in Vdsm check-merged > ---------------------------------------- > > Key: OVIRT-1442 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1442 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > I clicked on 'keep forever' so it won't go away if we want to debug. > On Wed, Jun 14, 2017 at 9:57 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7- > > x86_64/1967/console > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1442) Re: Build timed out in Vdsm check-merged
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1442?page=com.atlassian.jira.… ] eedri updated OVIRT-1442: ------------------------- Epic Link: OVIRT-400 > Re: Build timed out in Vdsm check-merged > ---------------------------------------- > > Key: OVIRT-1442 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1442 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > I clicked on 'keep forever' so it won't go away if we want to debug. > On Wed, Jun 14, 2017 at 9:57 AM, Milan Zamazal <mzamazal(a)redhat.com> wrote: > > Another "Build timed out": > > > > http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7- > > x86_64/1967/console > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1443) Create on-demand manual job for the metrics project
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1443?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1443: ---------------------------- Assignee: Gil Shinar (was: infra) we added build-on-demand job for the ovirt-metrics. closing. > Create on-demand manual job for the metrics project > --------------------------------------------------- > > Key: OVIRT-1443 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1443 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1461) Undesired repos within ovirt-master-snapshot
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1461?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1461: ---------------------------- Assignee: Barak Korren (was: infra) > Undesired repos within ovirt-master-snapshot > -------------------------------------------- > > Key: OVIRT-1461 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1461 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Barak Korren > > Please ensure el6, fc22, fc23 and fc24 repos are not added to > ovirt-master-snapshot. > Those are unsupported distributions on master. > I guess they're inherited from tested repo which should be cleaned as well. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1480?page=com.atlassian.jira.… ] eedri updated OVIRT-1480: ------------------------- Resolution: Fixed Status: Done (was: To Do) Fedora/Centos repos are occasionally down. We are handling most of the cases already with the oVirt mirrors, however, there are few flows that are not covered yet, each has its own ticket already. > Looks like Fedora mirrors are down > ---------------------------------- > > Key: OVIRT-1480 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: mirrors, repositories > > 23:25:48 + sudo yum -y install python34-PyYAML PyYAML > 23:25:48 Loaded plugins: fastestmirror > 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > Some notable failures: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… > http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… > And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7377 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_44_2053574495.1498568307604 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7377/, Build Number: 7377, Build Status: FAILURE ------=_Part_44_2053574495.1498568307604--

1 1

[JIRA] (OVIRT-1484) New VM for the Foreman project
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1484?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1484: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > New VM for the Foreman project > ------------------------------ > > Key: OVIRT-1484 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1484 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Michael Moll > Assignee: Evgheni Dereveanchin > Attachments: signature.asc > > > Hello, > I'd like to request another VM for the Foreman project, after we happily > are using two Jenkins slaves in your Infrastructure. :) > The name would be best "puppetmaster.theforeman.org", but we can also > use any other FQDN you're assigning, if that's easier for you. > The specs are: > minimum: 2 cores, 6 GiB RAM, 30 GiB space on / > optimum: 4 cores, 8 GiB RAM, 50 GiB space on / > OS: CentOS 7.3, x84_64 > As initial SSH keys, https://github.com/mmoll.keys can be used. > Thanks In Advance and Best Regards > -- > Michael Moll -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1483) Re: New VM for the Foreman project
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1483?page=com.atlassian.jira.… ] eedri updated OVIRT-1483: ------------------------- Resolution: Duplicate Status: Done (was: To Do) > Re: New VM for the Foreman project > ---------------------------------- > > Key: OVIRT-1483 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1483 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > Hi! > Adding Evgheni who manages the oVirt instance that manages the VMs. > On Tue, Jun 27, 2017 at 3:39 PM, Michael Moll <kvedulv(a)kvedulv.de> wrote: > > Hello, > > > > I'd like to request another VM for the Foreman project, after we happily > > are using two Jenkins slaves in your Infrastructure. :) > > > > The name would be best "puppetmaster.theforeman.org", but we can also > > use any other FQDN you're assigning, if that's easier for you. > > > > The specs are: > > minimum: 2 cores, 6 GiB RAM, 30 GiB space on / > > optimum: 4 cores, 8 GiB RAM, 50 GiB space on / > > OS: CentOS 7.3, x84_64 > > > > As initial SSH keys, https://github.com/mmoll.keys can be used. > > > > Thanks In Advance and Best Regards > > -- > > Michael Moll > > > -- > Eyal edri > ASSOCIATE MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1484) New VM for the Foreman project
by Michael Moll (oVirt JIRA) 27 Jun '17

27 Jun '17

Michael Moll created OVIRT-1484: ----------------------------------- Summary: New VM for the Foreman project Key: OVIRT-1484 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1484 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Michael Moll Assignee: infra Hello, I'd like to request another VM for the Foreman project, after we happily are using two Jenkins slaves in your Infrastructure. :) The name would be best "puppetmaster.theforeman.org", but we can also use any other FQDN you're assigning, if that's easier for you. The specs are: minimum: 2 cores, 6 GiB RAM, 30 GiB space on / optimum: 4 cores, 8 GiB RAM, 50 GiB space on / OS: CentOS 7.3, x84_64 As initial SSH keys, https://github.com/mmoll.keys can be used. Thanks In Advance and Best Regards -- Michael Moll -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1483) Re: New VM for the Foreman project
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

eedri created OVIRT-1483: ---------------------------- Summary: Re: New VM for the Foreman project Key: OVIRT-1483 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1483 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eedri Assignee: infra Hi! Adding Evgheni who manages the oVirt instance that manages the VMs. On Tue, Jun 27, 2017 at 3:39 PM, Michael Moll <kvedulv(a)kvedulv.de> wrote: > Hello, > > I'd like to request another VM for the Foreman project, after we happily > are using two Jenkins slaves in your Infrastructure. :) > > The name would be best "puppetmaster.theforeman.org", but we can also > use any other FQDN you're assigning, if that's easier for you. > > The specs are: > minimum: 2 cores, 6 GiB RAM, 30 GiB space on / > optimum: 4 cores, 8 GiB RAM, 50 GiB space on / > OS: CentOS 7.3, x84_64 > > As initial SSH keys, https://github.com/mmoll.keys can be used. > > Thanks In Advance and Best Regards > -- > Michael Moll > -- Eyal edri ASSOCIATE MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1475: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: Evgheni Dereveanchin > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri commented on OVIRT-1475: ------------------------------ I've sent https://gerrit.ovirt.org/#/c/78707/ to increase the build history for now. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1472) Add SSL to resources.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1472?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1472: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Add SSL to resources.ovirt.org > ------------------------------ > > Key: OVIRT-1472 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1472 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Priority: High > > This was already requested in the past, not sure why we didn't follow up. We need to allow users to D/L packages without fear of MITM attacks. > Package signing can help a little, but not everything is signed. (ISOs are not signed for example...) -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1482) document PHX OpenShift instance
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1482?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1482: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > document PHX OpenShift instance > ------------------------------- > > Key: OVIRT-1482 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1482 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Splitting from OVIRT-887 to document typical tasks of OpenShift management on readthedocs -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1482) document PHX OpenShift instance
by Evgheni Dereveanchin (oVirt JIRA) 27 Jun '17

27 Jun '17

Evgheni Dereveanchin created OVIRT-1482: ------------------------------------------- Summary: document PHX OpenShift instance Key: OVIRT-1482 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1482 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Splitting from OVIRT-887 to document typical tasks of OpenShift management on readthedocs -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7374 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_39_155569381.1498560833393 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7374/, Build Number: 7374, Build Status: FAILURE ------=_Part_39_155569381.1498560833393--

1 1

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #540
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/changes/13/75913/5:patch --prune > git rev-parse origin/patch^{commit} # timeout=10 > git rev-parse patch^{commit} # timeout=10 Checking out Revision 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f (patch) > git config core.sparsecheckout # timeout=10 > git checkout -f 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f > git rev-list 4b0fe3e0c9fba26cdbaafe2b29fddd3411225d6f # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/hudson5905322125246910724.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML repomd = self.metalink_data.repomd File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 916, in <lambda> metalink_data = property(fget=lambda self: self._getMetalink(), File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 904, in _getMetalink shutil.move(result, self.metalink_filename) File "/usr/lib64/python2.7/shutil.py", line 301, in move copy2(src, real_dst) File "/usr/lib64/python2.7/shutil.py", line 130, in copy2 copyfile(src, dst) File "/usr/lib64/python2.7/shutil.py", line 82, in copyfile with open(src, 'rb') as fsrc: IOError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-updates-fc24/metalink.xml.tmp' Build step 'Execute shell' marked build as failure

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7371 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

------=_Part_35_1165382954.1498553676617 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7371/, Build Number: 7371, Build Status: FAILURE ------=_Part_35_1165382954.1498553676617--

1 1

[JIRA] (OVIRT-1481) Move host key insertion to known_hosts before gerrit query
by Gil Shinar (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1481?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1481: --------------------------------- Assignee: Gil Shinar (was: infra) > Move host key insertion to known_hosts before gerrit query > ---------------------------------------------------------- > > Key: OVIRT-1481 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1481 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Gil Shinar > -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1481) Move host key insertion to known_hosts before gerrit query
by Gil Shinar (oVirt JIRA) 27 Jun '17

27 Jun '17

Gil Shinar created OVIRT-1481: --------------------------------- Summary: Move host key insertion to known_hosts before gerrit query Key: OVIRT-1481 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1481 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Gil Shinar Assignee: infra -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

Can't find gdeploy RPM under CentOS storage sig repo
by Daniel Belenky 27 Jun '17

27 Jun '17

Hi Sahina, My name is Daniel, im from the oVirt infra team. We are currently trying to find an official CentOS repo wich contains *gdeploy *RPMs. Usually we can find all the Gluster related RPMs under the Storage SIG repo, but couldn't find gdeploy there. Is it being released to the CentOS repos? Thanks, -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

4 6

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1480?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1480: -------------------------------- Labels: mirrors repositories (was: ) > Looks like Fedora mirrors are down > ---------------------------------- > > Key: OVIRT-1480 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > Labels: mirrors, repositories > > 23:25:48 + sudo yum -y install python34-PyYAML PyYAML > 23:25:48 Loaded plugins: fastestmirror > 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > Some notable failures: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… > http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… > And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1480?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1480: -------------------------------- Component/s: oVirt Infra > Looks like Fedora mirrors are down > ---------------------------------- > > Key: OVIRT-1480 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: oVirt Infra > Reporter: ngoldin(a)redhat.com > Assignee: infra > > 23:25:48 + sudo yum -y install python34-PyYAML PyYAML > 23:25:48 Loaded plugins: fastestmirror > 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > Some notable failures: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… > http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… > And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1480?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1480: -------------------------------- Issue Type: Outage (was: By-EMAIL) > Looks like Fedora mirrors are down > ---------------------------------- > > Key: OVIRT-1480 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: ngoldin(a)redhat.com > Assignee: infra > > 23:25:48 + sudo yum -y install python34-PyYAML PyYAML > 23:25:48 Loaded plugins: fastestmirror > 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > Some notable failures: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… > http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… > And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by Barak Korren (oVirt JIRA) 27 Jun '17

27 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1480?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1480: ------------------------------------- [~dbelenky(a)redhat.com] do we have an open ticket to remove that link to copr and replace it with a properly mirrored repo? > Looks like Fedora mirrors are down > ---------------------------------- > > Key: OVIRT-1480 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: ngoldin(a)redhat.com > Assignee: infra > > 23:25:48 + sudo yum -y install python34-PyYAML PyYAML > 23:25:48 Loaded plugins: fastestmirror > 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > Some notable failures: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… > http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… > And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

Change 78588,5 (vdsm) failed system tests
by oVirt Jenkins 27 Jun '17

27 Jun '17

Change 78588,5 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78588/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/930/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7364 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 27 Jun '17

27 Jun '17

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7364/, Build Number: 7364, Build Status: FAILURE

1 4

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1777 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_15_721368267.1498526913233 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/1777/, Build Number: 1777, Build Status: FAILURE ------=_Part_15_721368267.1498526913233--

1 1

[JIRA] (OVIRT-1480) Looks like Fedora mirrors are down
by ngoldin＠redhat.com (oVirt JIRA) 26 Jun '17

26 Jun '17

ngoldin(a)redhat.com created OVIRT-1480: ----------------------------------------- Summary: Looks like Fedora mirrors are down Key: OVIRT-1480 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1480 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: ngoldin(a)redhat.com Assignee: infra 23:25:48 + sudo yum -y install python34-PyYAML PyYAML 23:25:48 Loaded plugins: fastestmirror 23:25:51 http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: [Errno 14] curl#7 - "Failed connect to copr-be.cloud.fedoraproject.org:80; No route to host" Some notable failures: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/testRepor… http://jenkins.ovirt.org/job/lago_master_github_check-merged-el7-x86_64/146… And several more. Hopefully just a glitch. -- This message was sent by Atlassian JIRA (v1000.1089.0#100053)

1 0

Change 78591,7 (vdsm) failed system tests
by oVirt Jenkins 26 Jun '17

26 Jun '17

Change 78591,7 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/78591/7 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/928/

1 0

oVirt infra daily report - unstable production jobs - 365
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_2_1509536356.1498518002677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/365//artifact/exported-a… Cheers, Jenkins ------=_Part_2_1509536356.1498518002677 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 26/06/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_4.1_image-ng-system-tests/">ovirt_4.1_image-ng-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_2_1509536356.1498518002677--

1 0

Planned restart of production services
by Evgheni Dereveanchin 26 Jun '17

26 Jun '17

Hi everyone, I'll be restarting several production systems today to apply OS updates. The following services may be unreachable for some period of time: - resources.ovirt.org - software repositories - jenkins.ovirt.org - CI master No new builds will be started during this period. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

[oVirt Jenkins] ovirt_4.1_hc-system-tests - Build # 111 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_718_183277066.1498186159562 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_4.1_hc-system-tests/111/ Build Number: 111 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #111 [Yaniv Kaul] Move disks to be ext4 based instead of XFS ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_718_183277066.1498186159562--

1 6

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7362 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_852_76941207.1498503998016 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7362/, Build Number: 7362, Build Status: FAILURE ------=_Part_852_76941207.1498503998016--

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri edited comment on OVIRT-1475 at 6/26/17 9:35 PM: ------------------------------------------------------- The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for "{project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts}" was (Author: eedri): The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for {project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts} > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri edited comment on OVIRT-1475 at 6/26/17 9:34 PM: ------------------------------------------------------- The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for {project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts} was (Author: eedri): The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for '{project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts}'. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri commented on OVIRT-1475: ------------------------------ The retention policy is defined in the templates (under jobs/conf/yaml/templates), look for '{project}_{version}_build-artifacts-{distro}-{arch}{_big_artifacts}'. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1391) Add repo injection capabilities to STD-CI
by Daniel Belenky (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1391?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1391: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Add repo injection capabilities to STD-CI > ----------------------------------------- > > Key: OVIRT-1391 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1391 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > Labels: containers, mock_runner.sh, standard-ci > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > We want to add to standard-CI ('{{mock-runner.sh}}') the capability to provide a project with information about package repositories that unrelated to the setup of the environment that standard-CI scripts run in. > A projects will specify required repositories by including one or more files that match the pattern “{{automation/$STD_CI_STAGE.\*.yumrepos.\*}}”, where “{{$STG_CI_STAGE}}” is e.g “{{build-system-artifacts}}” and the wildcard sections can be omitted along with the dots that precede them. The file should be in the format of a yum configuration file and include configuration for required yum repositories. To avoid the projects having to maintain URLs for yum repositories, the file may contain configurations without repository URLs specified and with the “skip_if_unavailable” parameter set to “true”. Only the names of the repository configuration sections will be meaningful for the purpose of the CI system. For each such file the CI system will: > # Replace any configuration section that defines the “{{ovirt-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt packages for the distribution identified by "{{<distro-id>}}" may be obtained. “{{<distro-id>}}" will be a string such as “el7” or “fc25”. To allow avoiding collisions with the released oVirt yum configuration, the “{{ovirt-ci-<repoid>}}” and “{{ovirt-experimental-<repoid>}}” configuration section will be treated the same way. > # Replace any configuration section that defines the “{{ovirt-dependencies-<distro-id>}}” repository with one or more configuration sections pointing to repositories from which oVirt dependency packages need to be obtained. These will include, among others, base operating system packages. The “{{ovirt-ci-dependencies-<repoid>}}” and “{{ovirt-experimental-dependencies-<repoid>}}” configuration section will be treated the same way. > # Run the mirror injection process. Any repository handled by this process will have the the “{{skip_if_unavailable}}” parameter removed if specified (To make the default value of “{{false}}” come into effect). > # Prepend a “{{\[main]}}” section that disables the use of the “{{/etc/yum.repos.d}}” directory. This will allow the file to appended to the "{{/etc/yun.conf}}” file to automatically disable all internet-facing preconfigured repositories. > To allow automation scripts to find the repository files prepared for them, several environment variables will be made available in the Standard-CI runtime environment: > # {{STD_CI_STAGE}}: Will contain the name of the Standard-CI stage, e.g. “{{build-artifacts}}”. > # {{STD_CI_DISTRO}}: Will contain the distribution version identifier (e.g “el7” or “fc25”) of the Standard-CI runtime. > # {{STD_CI_YUMREPOS}}: Will point to an existing “{{*.yumrepos}}” file that most closely matches the current running stage and distribution -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[oVirt Jenkins] standard-enqueue - Build #2002 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_849_924255919.1498487460705 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/2002/ Build Name: 2002 ovirt-engine-extension-aaa-jdbc (4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/78366 - title: Fix encrypted option in password-reset - project: ovirt-engine-extension-aaa-jdbc - branch: master - author: Miroslava Voglova <mvoglova(a)redhat.com> ------=_Part_849_924255919.1498487460705--

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by Evgheni Dereveanchin (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1475: --------------------------------------------- I don't see any retention settings in the [job configuration yaml|https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=blob;f=jobs/confs/proj…] and not entirely sure where they're inherited from. As for build #97 - it is marked with the "keep this build forever" tag, that's why it was not deleted. > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[oVirt Jenkins] ovirt_master_hc-system-tests - Build # 141 - Failure!
by jenkins＠jenkins.phx.ovirt.org 26 Jun '17

26 Jun '17

------=_Part_600_1684416853.1498014845835 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_hc-system-tests/141/ Build Number: 141 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #141 [Shani Leviim] Remove 'provisioned_size' disk parameter [Shirly Radco] ovirt-engine-metrics: add build-on-demand job ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 002_bootstrap.py.junit.xml.[empty] Error Message: Stack Trace: Test report file /home/jenkins/workspace/ovirt_master_hc-system-tests/exported-artifacts/002_bootstrap.py.junit.xml was length 0 ------=_Part_600_1684416853.1498014845835--

1 11

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by Yuval Turgeman (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-1475: --------------------------------------- There were more than 2 builds in the job's history after Sep 2016... why did it save that single job from 2016 ? > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by eedri (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] eedri commented on OVIRT-1475: ------------------------------ Can you check what is the current configuration in YAML for keeping history for this job? > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0

[JIRA] (OVIRT-1475) Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_64/447/ wasn't time triggered for months
by Evgheni Dereveanchin (oVirt JIRA) 26 Jun '17

26 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1475?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1475: --------------------------------------------- This job has "Max # of builds to keep" equal to 2 so all older builds are deleted by Jenkins itself. I do not see any "max-total: 2" configuration in our YAMLs so not sure when this change was introduced. Recent job config history doesn't have anything related to changes in this parameter: http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > Check why http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… wasn't time triggered for months > ---------------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1475 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1475 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: High > > The follow job http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… is defined to run nightly (00 04 * * *) but for some reason didn't run for 9 months(!). > We need to investigate why it didn't run and maybe find some clues in the logs. > cc [~sbonazzo(a)redhat.com] -- This message was sent by Atlassian JIRA (v1000.1085.0#100052)

1 0