July 2017 - Infra - oVirt List Archives

[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