July 2017 - Infra - oVirt List Archives

[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