- Infra - oVirt List Archives

[JIRA] (OVIRT-713) Clean reposync directory after n times of sync failure
by ngoldin＠redhat.com (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-713?page=com.atlassian.jira.p… ] ngoldin(a)redhat.com commented on OVIRT-713: ------------------------------------------ I didn't see any failures with this at least in the past 2 months. We added some fixes to reposync flow, but that was a while ago. > Clean reposync directory after n times of sync failure > ------------------------------------------------------ > > Key: OVIRT-713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-713 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: infra > > Sometimes reposync fail to sync rpms that already been synced. > To resolve this issue, lago removes those rpms, and runs reposync again. > This resolution doesn't always work, and then we need to clean all the rpms that were synced. > We want lago to clear the cached rpms after n times of sync failure, and then try to sync again. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78631,13 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78631,13 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78631/13 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1049/

1 0

Change 78837,4 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78837,4 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78837/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1047/

1 0

Change 78890,3 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78890,3 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78890/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1039/

1 0

[JIRA] (OVIRT-1434) Re: Every user can abandon patches that are not his
by Shlomo Ben David (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1434?page=com.atlassian.jira.… ] Shlomo Ben David updated OVIRT-1434: ------------------------------------ Resolution: Fixed Status: Done (was: To Do) > 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.1092.1#100053)

1 0

[JIRA] (OVIRT-1434) Re: Every user can abandon patches that are not his
by Shlomo Ben David (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1434?page=com.atlassian.jira.… ] Shlomo Ben David commented on OVIRT-1434: ----------------------------------------- yes, with this patch: https://gerrit.ovirt.org/#/c/77941/ > 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.1092.1#100053)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #1800 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

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

1 1

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1252: ------------------------------------- [~eedri] yes. for when using build-artifats as a yum repo with the latestStableBuild link. > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1162: ------------------------------------- [~eedri] actually I made the nightly publisher jobs check if cron ran and fail (with unstable) otherwise when I made it sync from tested. So this is probably not highly needed any more. > Make sure cron failure email from resources.ovirt.org reach the infra list > -------------------------------------------------------------------------- > > Key: OVIRT-1162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are quite a few things that run there with cron and we need to know when they fail. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-886: ------------------------------------ [~eedri] no this is actually a known issue, ticket should remain open. It can be easily fixed as long as we're using mock though. > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- [~eedri(a)redaht.com] actually it seems I linked to the wrong one. Which ticket are we using to track V2 again? > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1014: ------------------------------------- [~eedri] linking. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1014: -------------------------------- Labels: standard-ci (was: ) > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > Labels: standard-ci > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1014: -------------------------------- Component/s: oVirt CI > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1064) Re-factor experimental groovy script
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1064?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1064: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) Closing this ticket because the 'experimental' flow will be deprecated by the 'change-queue' flow. > Re-factor experimental groovy script > ------------------------------------ > > Key: OVIRT-1064 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1064 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > The experimental Groovy scripts has several issues that should be resolved by re-factoring it: > # Turn the variables defined in the top of the file into constants with upper case manes to ensure they're not used in functions by mistake > # Remove unused arguments from functions > # Move the main() function definition to the top of the file so its easier to quickly see an overview of the whole flow > # Use the "global" constants inside main() instead of passing gazillion parameters to it. > # Pass parameters directly to function instead of turning them into strings and using interpolation > # Use 'for-each' loops instead of C-style indexed loops. > # Use consistent indention throughout the file -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

Change 78189,11 (vdsm) failed system tests
by oVirt Jenkins 03 Jul '17

03 Jul '17

A system test invoked by the "ovirt-master" change queue including change 78189,11 (vdsm) failed. However, this change seems not to be to root cause for failure. Change 78630,13 (vdsm) that this change depends on or is based on, was detected to cause testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 78630,13 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/78189/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/78630/13 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1037/

1 0

[JIRA] (OVIRT-1396) Add a new 'test-system-artifacts' Standard-CI stage
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1396?page=com.atlassian.jira.… ] eedri updated OVIRT-1396: ------------------------- Priority: High (was: Medium) > Add a new 'test-system-artifacts' Standard-CI stage > --------------------------------------------------- > > Key: OVIRT-1396 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1396 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Priority: High > > This is a part of [containers CI/CD|https://docs.google.com/a/redhat.com/document/d/1mEo3E0kRvlUWT9VaSPKD…] flow implementation process. > An order to allow building and testing processes for containers to be triggered after package that are needed for them are built, we will introduce the "{{test-system-artifacts}}" standard-CI stage. > This stage will be invoked from the 'experimental' or 'change-queue-tester' pipelines jost like the existing OST-based flows. > In order to provide package and repo information to the std-CI script invoked by this stage we well need to implement OVIRT-1391 -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1292) make ovirt-release RPMs RHEL compatible
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1292?page=com.atlassian.jira.… ] eedri commented on OVIRT-1292: ------------------------------ [~sbonazzo(a)redhat.com] is there anything we can do in the release rpm to fix it? > make ovirt-release RPMs RHEL compatible > --------------------------------------- > > Key: OVIRT-1292 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1292 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > > Some oVirt users are using the ovirt-release el7 RPMs to test oVirt on RHEL. > Unfortunately, RHEL uses the '7Server' link which doesn't exist in CentOS resulting in breakage like: > 'http://mirror.centos.org/centos/7Server/virt/x86_64/kvm-common/' > while 'http://mirror.centos.org/centos/7/virt/x86_64/kvm-common/' exist > We should either ask CentOS to add that link on the repo or find a way to fix it ourselves in the release rpm. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] eedri updated OVIRT-1276: ------------------------- Issue Type: Improvement (was: By-EMAIL) > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: rgolan(a)redhat.com > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1276) generate a link to OST automation job
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1276?page=com.atlassian.jira.… ] eedri commented on OVIRT-1276: ------------------------------ I'm guessing you mean 'ci please build' and not 'ci please help', and you want us to add a link to the manual OST job, right? We need to check the YAML templates and see what is the best way to do it. > generate a link to OST automation job > ------------------------------------- > > Key: OVIRT-1276 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1276 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: rgolan(a)redhat.com > Assignee: infra > > When activating the 'ci please help' robo verb, please generate a link with > job parameters for the ost job: > Say I told the robot to build my 4.1 patch, than asside from the aftifact > link, create a a link to trigger the ost job with refs/to/spec. pick 4.1 as > a release and so on. In that way a user is a click away from firing a job. > This could be then continued with 'ci please build and ost' kinda of thing > \R -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] eedri commented on OVIRT-1252: ------------------------------ [~bkorren(a)redhat.com] is this still relevant after the deployment of the new logic of deploy rpms? > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1218) Merge infra-docs into the 'jenkins' repo
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1218?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1218: ---------------------------- Assignee: Dafna Ron (was: infra) good practice on git commands > Merge infra-docs into the 'jenkins' repo > ---------------------------------------- > > Key: OVIRT-1218 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1218 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Dafna Ron > Labels: documentation > > The 'jenkins' repo currently contains no documentation. The 'infra-docs' contains only docs, most of which deal with stuff that is in the 'jenkins' repo. > Both repos are maintained by the exact same people (The oVirt infra team). > Therefore it makes sense to unify these repos. > Pros: > * Easier discovery of docs for people looking to contribute to the 'jenkins' repo. > * Can now enforce including documentation for new features in 'jenkins' repo. > * Less repos to maintain for the infra team. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.… ] eedri updated OVIRT-1162: ------------------------- Priority: High (was: Medium) > Make sure cron failure email from resources.ovirt.org reach the infra list > -------------------------------------------------------------------------- > > Key: OVIRT-1162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > > There are quite a few things that run there with cron and we need to know when they fail. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1183) Reinstall some of the Jenkins hypervisors in PHX as ovirt-node
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1183?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1183: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Reinstall some of the Jenkins hypervisors in PHX as ovirt-node > --------------------------------------------------------------- > > Key: OVIRT-1183 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1183 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Since we're running oVirt in PHX and already managed to find critical bugs due to it, > It would be nice to have a few hypervisors running ovirt-node instead of CentOS. > We can use it for Jenkins DC at first to see how it goes. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri updated OVIRT-1500: ------------------------- Priority: Low (was: Medium) > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > Priority: Low > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri commented on OVIRT-1500: ------------------------------ I'll lower priority and keep it for a while in case it pops again, if its not common then we will probably close it. Thanks for reporting anyway! > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1076) Create jobs to link Jira to Gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1076?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1076: ---------------------------- Assignee: Dafna Ron (was: infra) This can be a cool coding task to try out. It will require learning a bit the JIRA API and also to get familiar with the Gerrit python API we already use on other jobs. > Create jobs to link Jira to Gerrit > ---------------------------------- > > Key: OVIRT-1076 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1076 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: Dafna Ron > > Jira probably has an API, so we can make jobs that will find Gerrit patches with 'Jira-Ticket' header and link that to the matching Jira ticket. > We can also perhaps make the link show the patch status and be updated as the patch status changes. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1061) Update http://monitoring.ovirt.org/ovirt.apps/
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1061?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1061: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) probably best to remove it and make sure all our services are documented in infra-docs instead. > Update http://monitoring.ovirt.org/ovirt.apps/ > ---------------------------------------------- > > Key: OVIRT-1061 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1061 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > Please update http://monitoring.ovirt.org/ovirt.apps/ with all monitoring > and production services currently being used in oVirt infra. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1408) Please remove github/ovirt-web-ui from standard CI
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1408?page=com.atlassian.jira.… ] eedri updated OVIRT-1408: ------------------------- Resolution: Fixed Status: Done (was: To Do) > Please remove github/ovirt-web-ui from standard CI > -------------------------------------------------- > > Key: OVIRT-1408 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1408 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Marek Libra > Assignee: infra > > Please remove github/ovirt-web-ui from standard CI since Travis is used instead. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1425) Decrease global timeouts from 6h to 2h
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1425?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1425: ---------------------------- Assignee: Dafna Ron (was: infra) > Decrease global timeouts from 6h to 2h > -------------------------------------- > > Key: OVIRT-1425 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1425 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Dafna Ron > Labels: standard-ci > > The timeout is currently 6h, this was needed back when we had very long upgrade jobs. > We should probably decrease it to 2h, or maybe even less. Most stuff we have these days shouldn't be running more then ~40m. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] eedri updated OVIRT-1170: ------------------------- Blocked By: waiting for user feedback Status: Blocked (was: To Do) > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: gshereme(a)redhat.com > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1155?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1155: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Please enable https on resources.ovirt.org > ------------------------------------------ > > Key: OVIRT-1155 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Priority: High > > If no technical issue is preventing us to enable https, please enable it > for resources.ovirt.org. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1155) Please enable https on resources.ovirt.org
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1155?page=com.atlassian.jira.… ] eedri updated OVIRT-1155: ------------------------- Priority: High (was: Medium) > Please enable https on resources.ovirt.org > ------------------------------------------ > > Key: OVIRT-1155 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1155 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > Priority: High > > If no technical issue is preventing us to enable https, please enable it > for resources.ovirt.org. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1099) request for admin permissions on jenkins staging
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1099?page=com.atlassian.jira.… ] eedri updated OVIRT-1099: ------------------------- Resolution: Done Status: Done (was: To Do) > request for admin permissions on jenkins staging > ------------------------------------------------ > > Key: OVIRT-1099 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1099 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: infra > > Hi, > Can you please give me admin rights on the jenkins staging instance? > I'll like to review the new BlueOcean and do some tests there. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1087) drop gerrit log watch emails in favor or real monitoring
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1087?page=com.atlassian.jira.… ] eedri reassigned OVIRT-1087: ---------------------------- Assignee: Evgheni Dereveanchin (was: infra) > drop gerrit log watch emails in favor or real monitoring > -------------------------------------------------------- > > Key: OVIRT-1087 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1087 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: Evgheni Dereveanchin > > Right now Gerrit sends regular emails from log-watch with various info, such as [1]. > We need to go over these alerts and see if some make sense to convert to alerts on nagios and disable the rest. > [1]. > /changes/67155/revisions/57f6a24d70230c5e7 ... README/reviewed: 2 Time(s) > /changes/67587/revisions/807e4950b3a74d127 ... 6f9f5be2/rebase: 1 Time(s) > /changes/68315/revisions/182e8209319a41adc ... kefile/reviewed: 2 Time(s) > /changes/70704/edit?list: 1 Time(s) > /changes/71065/reviewers/1001042: 1 Time(s) > /changes/71129/revisions/07edcd447865468bc ... 086f7545/drafts: 2 Time(s) > /changes/71315/reviewers/1000458: 1 Time(s) > /changes/71337/revisions/3f37d51915b0c7235 ... 829ed631/submit: 1 Time(s) > /changes/?q=change:70704+has:draft&O=0: 1 Time(s) > /changes/?q=is:open+owner:self&q=is:open+r ... +limit:10&O=881: 2 Time(s) > 404 Not Found > /changes/55626/detail?O=50004: 1 Time(s) > /changes/70594/detail?O=50004: 2 Time(s) > /changes/71272/detail?O=50004: 1 Time(s) > /gerrit_ui/undefined.cache.js: 1 Time(s) > /ovirt-system-tests: 2 Time(s) -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by Allon Mureinik (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] Allon Mureinik commented on OVIRT-1500: --------------------------------------- [~eedri] This is the first time I encountered it. If it's not worth the tradeoff, we can close the ticket - that's your call to make. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1064) Re-factor experimental groovy script
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1064?page=com.atlassian.jira.… ] eedri commented on OVIRT-1064: ------------------------------ [~bkorren(a)redhat.com] is this in progress or done perhaps? > Re-factor experimental groovy script > ------------------------------------ > > Key: OVIRT-1064 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1064 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > > The experimental Groovy scripts has several issues that should be resolved by re-factoring it: > # Turn the variables defined in the top of the file into constants with upper case manes to ensure they're not used in functions by mistake > # Remove unused arguments from functions > # Move the main() function definition to the top of the file so its easier to quickly see an overview of the whole flow > # Use the "global" constants inside main() instead of passing gazillion parameters to it. > # Pass parameters directly to function instead of turning them into strings and using interpolation > # Use 'for-each' loops instead of C-style indexed loops. > # Use consistent indention throughout the file -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1033) The ovirt-engine findbugs job is restricted to running on el7||fc23 slaves
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1033?page=com.atlassian.jira.… ] eedri updated OVIRT-1033: ------------------------- Resolution: Fixed Status: Done (was: To Do) findbugs moved to check-patch.sh, so it will run on all the nodes defined in the project file > The ovirt-engine findbugs job is restricted to running on el7||fc23 slaves > -------------------------------------------------------------------------- > > Key: OVIRT-1033 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1033 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > We should let it run on any slave if possible -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1014) avoid repetition in automation/*packages
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1014?page=com.atlassian.jira.… ] eedri commented on OVIRT-1014: ------------------------------ [~danken(a)redhat.com] does this requirement is still needed? [~bkorren(a)redhat.com] if its still relevant, maybe worth attaching it to the main ticket for V2 std-ci. > avoid repetition in automation/*packages > ---------------------------------------- > > Key: OVIRT-1014 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1014 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: danken > Assignee: infra > > Currently we have many automation/*packages* files, mostly repeating each other. > Most of the information there is then repeated in vdsm.spec as well. > It would be nice to have a hierarchical way to define packages. E.g. having most packages in automation/build-artifacts-manual.packages, and adding el7-specific dependencies in avoid repetition in automation/build-artifacts-manual.packages.el7. > It would be even better to have a single palce (yaml file?) to declare each required package and its version, for each platform/architecture. We can then use it to generate the spec file. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1007) repo closure job should find also optional pkg
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1007?page=com.atlassian.jira.… ] eedri updated OVIRT-1007: ------------------------- Priority: Low (was: Medium) > repo closure job should find also optional pkg > ---------------------------------------------- > > Key: OVIRT-1007 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1007 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Priority: Low > > http://jenkins.ovirt.org/job/repos_4.1_check-closure_el7_merged/38/console -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-974) Document ovirt.org hosting info and troubleshooting
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-974?page=com.atlassian.jira.p… ] eedri reassigned OVIRT-974: --------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Document ovirt.org hosting info and troubleshooting > --------------------------------------------------- > > Key: OVIRT-974 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-974 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eedri > Assignee: Marc Dequènes (Duck) > > Currently ovirt.org is hosted on OpenShift gear and managed by OSAS. > We need to document the procedure on how to fix issues on it when they arrise and list contact persons who can help. > [~ederevea] maybe documenting it on infra-docs is a good idea. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1009) Re: When trigged manually the check-merged job
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1009?page=com.atlassian.jira.… ] eedri updated OVIRT-1009: ------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) please reopen if you see it again and provide details. > Re: When trigged manually the check-merged job > ---------------------------------------------- > > Key: OVIRT-1009 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1009 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eedri > Assignee: infra > > Adding infra-support to open a ticket on it. > But it will help if you'll provide example of what you are expecting to see > so we'll check its possible. > On Mon, Jan 9, 2017 at 11:32 AM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > When trigged manually the check-merged job for specific patch we don't see > > the link in the patch History - see in https://gerrit.ovirt.org/#/ > > c/69802/3 > > > > it used to be different .. can we get the link back? > > > > Thanks. > > > > -- > > *Yaniv Bronhaim.* > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-844) move node builds jobs to run on Lago VM
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-844?page=com.atlassian.jira.p… ] eedri updated OVIRT-844: ------------------------ Resolution: Won't Do Status: Done (was: To Do) Lago isn't relevant here, livecdcreator is used for PXE installation to build the image. > move node builds jobs to run on Lago VM > --------------------------------------- > > Key: OVIRT-844 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-844 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eedri > Assignee: infra > > the node jobs keeps failing on cleanup issues which will be solved if we move the job to run on Lago. > lets do it for master(4.1) as POC and see if it helps. > http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6… > the job doesn't nessasarily needs a BM slave, so we will need to check what infra changes are needed (puppet classes to install lago?) in order to run it. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] eedri updated OVIRT-886: ------------------------ Resolution: Cannot Reproduce Status: Done (was: To Do) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gil Shinar > Assignee: infra > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-926) check why 3.6 experimental job failed even if not error in shown on job
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-926?page=com.atlassian.jira.p… ] eedri updated OVIRT-926: ------------------------ Resolution: Cannot Reproduce Status: Done (was: To Do) > check why 3.6 experimental job failed even if not error in shown on job > ----------------------------------------------------------------------- > > Key: OVIRT-926 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-926 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eedri > Assignee: infra > Labels: ost_failures > > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4322/ > [~gbenhaim@redhat.com][~ngoldin@redhat.com][~ederevea][~bkorren@redhat.com] any ideas? -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1500) CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1500?page=com.atlassian.jira.… ] eedri commented on OVIRT-1500: ------------------------------ [~mureinik] how often are you hitting this issue? If we will enable Jenkins jobs to run also on changes w/o 'code change' it might have a significant impact on the CI resources and potentially increase the number of jobs running on CI ( w/o a real code change ) and will result in longer waiting time per job. > CI on ovirt-engine patch succeeded, but didn't mark CI=+1 on gerrit > ------------------------------------------------------------------- > > Key: OVIRT-1500 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1500 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: Allon Mureinik > Assignee: infra > > In my recent engine patch https://gerrit.ovirt.org/#/c/78911 the CI passed, but was not marked as so in gerrit. > Looking through gerrit's history, here's what I *think* is going on: > 08:41 - patchset #1 is submitted > 08:41 - CI (check-patch) starts for both EL7 and fc25 > _At this point I noticed a typo in the commit method. I fixed it and posted patchset #2_ > 08:42 - patchset #2 is submitted > _CI was never triggered for patchset #2. Is this because the only difference between it and patchset #1 is the commit message?_ > 09:15 - CI for patchset #1 completes, and marks *patchset #1* with CI=+1. This is not inherited to patchset #2 for some reason. > Expected behavior: > If CI for patchset #1 passed and the only difference is the commit message (not the parent commit and not the content), I'd expect the CI score to be inherited. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[oVirt Jenkins] ovirt_master_he-system-tests - Build # 4 - Failure!
by jenkins＠jenkins.phx.ovirt.org 03 Jul '17

03 Jul '17

------=_Part_23_1284566956.1498532238623 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/ Build: http://jenkins.ovirt.org/job/ovirt_master_he-system-tests/4/ Build Number: 4 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #4 [ngoldin] image-ng-suite: add distro on generated images ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_23_1284566956.1498532238623--

1 7

[JIRA] (OVIRT-682) Improve CI logging
by eedri (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-682?page=com.atlassian.jira.p… ] eedri updated OVIRT-682: ------------------------ Priority: Low (was: Medium) > Improve CI logging > ------------------ > > Key: OVIRT-682 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-682 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: eedri > Assignee: infra > Priority: Low > Labels: standard-ci > > On Fri, Aug 12, 2016 at 8:08 PM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > Hi all, > > > > Lately vdsm builds are failing in the install packages stage with > > this unhelpful error: > > > > 13:59:42 INFO: installing package(s): autoconf automake gdb ... > > 13:59:53 ERROR: Command failed. See logs for output. > > > > I downloaded the logs.tgz file from > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/artifact/exported-artifacts/logs.tgz > > > > And indeed in /./vdsm/logs/mocker-fedora-24-x86_64.fc24.install_packages/ > > root.log > > I found found this error: > > > > DEBUG util.py:421: Error: Package: > > python-ioprocess-0.17.0-1.201608111609.gitbd272f2.fc24.noarch > > (ovirt-snapshot) > > DEBUG util.py:421: Requires: ioprocess = > > 0.17.0-1.201608111609.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.15.1-1.fc24.x86_64 (fedora) > > DEBUG util.py:421: ioprocess = 0.15.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.16.1-1.fc24.x86_64 (updates) > > DEBUG util.py:421: ioprocess = 0.16.1-1.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201607121058.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201607121058.gitbd272f2.fc24 > > DEBUG util.py:421: Available: > > ioprocess-0.17.0-1.201608111129.gitbd272f2.fc24.x86_64 > > (ovirt-snapshot) > > DEBUG util.py:421: ioprocess = > > 0.17.0-1.201608111129.gitbd272f2.fc24 > > > > So we have 2 issues here: > > > > 1. We need *all* errors in the console > > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24- > > x86_64/1154/console > Not sure its possible or easy to do, these errors usually come from mock > and are not relevant to the code running on the console. > I've cc'd infra-support and updated topic to track it and check our options. > Going foward, we might want to install a log collector like logstash and > then searching errors there should be much easier. > > > > > > 2. Someone need to fix the ovirt-snapshot repository - it should have > > the missing ioprocess > > package. > > Maybe the project xml is not correct? > > > > Nir > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Component/s: Gerrit/git > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Gerrit/git, oVirt CI > Reporter: ybronhei > Assignee: infra > Labels: gerrit, jenkins > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0

[JIRA] (OVIRT-1502) gerrit does not print check_merged output
by Barak Korren (oVirt JIRA) 03 Jul '17

03 Jul '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1502?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1502: -------------------------------- Labels: gerrit jenkins (was: gerrit) > gerrit does not print check_merged output > ----------------------------------------- > > Key: OVIRT-1502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1502 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: ybronhei > Assignee: infra > Labels: gerrit, jenkins > > Hello, > Recently vdsm gerrit job check-merged doesn't send report after its done - > check all recent jobs - they were done but the gerrit url doesn't show the > output nor send email about failures. > Thanks in advance > Yaniv Bronhaim. > -- > Yaniv Bronhaim. -- This message was sent by Atlassian JIRA (v1000.1092.1#100053)

1 0