- Infra - oVirt List Archives

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1448: ------------------------------------- Created [a patch|https://gerrit.ovirt.org/78277] to fix a code issue that would have prevented us from properly implementing dependencies for merged Gerrit changes. > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1448: ------------------------------------- Here are some docs about how this is done in OpenStack: https://docs.openstack.org/infra/manual/developers.html#cross-repository-de… The basic Idea is that developers add a '{{Depends-On:}}' header to the commit message follows by a 40-char Gerrit change ID. One implication of this is that the same change ID can point to multiple changes (same change in different branches), so we will need to query Gerrit and find all actual changes with that ID. > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1457) Add user to white list for jenkins jobs to run
by Gil Shinar (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1457?page=com.atlassian.jira.… ] Gil Shinar reassigned OVIRT-1457: --------------------------------- Assignee: Gil Shinar (was: infra) > Add user to white list for jenkins jobs to run > ---------------------------------------------- > > Key: OVIRT-1457 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1457 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Maor Lipchuk > Assignee: Gil Shinar > > User name: shubham dubey > email: dubey504(a)gmail.com > Thanks, > Maor -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1457) Add user to white list for jenkins jobs to run
by Maor Lipchuk (oVirt JIRA) 18 Jun '17

18 Jun '17

Maor Lipchuk created OVIRT-1457: ----------------------------------- Summary: Add user to white list for jenkins jobs to run Key: OVIRT-1457 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1457 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Maor Lipchuk Assignee: infra User name: shubham dubey email: dubey504(a)gmail.com Thanks, Maor -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

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

18 Jun '17

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

1 1

Please avoid manual modification to the 'tested' repo
by Barak Korren 18 Jun '17

18 Jun '17

After working to make the new 'fluentd' package available to 'experimental' we noticed it kept on failing. This morning I looked into the logs and found out it was failing because 'reposync' was getting 404 errors on downloading 'qemu-kvm-ev' and other packages from the 'tested' repo. I restored the missing packages from 'experimental' and the errors went away. Looking deeper into this I found the following in the history file on resources: find /var/www/html/repos/ovirt/tested/master/rpm/el7/ -name "qemu-kvm*"|xargs rm -f I'm sure who did this meant well, but this just broke stuff, and at a time where we are desperately trying to make things stable again. Please avoid touching the 'tested' repo manually, the creation processes for it are rather complex for various reasons (Wost of which have to do with enabling it to be usable while still constantly adding updates to it). -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

2 2

[JIRA] (OVIRT-1456) deep dive about OST package management
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1456?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1456: ----------------------------------- Assignee: Barak Korren (was: infra) > deep dive about OST package management > -------------------------------------- > > Key: OVIRT-1456 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1456 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: mirrors, ost, standard-ci > > Very few people understand how OST collects the packages it tests, and there is a lot of confusion about this. > Lets do a deep dive to teach people how it works. > We shall talk about: > # repoman > # the CI mirrors > # the reposync process lago runs and the reposync files in OST -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1456) deep dive about OST package management
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

Barak Korren created OVIRT-1456: ----------------------------------- Summary: deep dive about OST package management Key: OVIRT-1456 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1456 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Very few people understand how OST collects the packages it tests, and there is a lot of confusion about this. Lets do a deep dive to teach people how it works. We shall talk about: # repoman # the CI mirrors # the reposync process lago runs and the reposync files in OST -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1456) deep dive about OST package management
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1456?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1456: -------------------------------- Epic Link: OVIRT-400 > deep dive about OST package management > -------------------------------------- > > Key: OVIRT-1456 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1456 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: mirrors, ost, standard-ci > > Very few people understand how OST collects the packages it tests, and there is a lot of confusion about this. > Lets do a deep dive to teach people how it works. > We shall talk about: > # repoman > # the CI mirrors > # the reposync process lago runs and the reposync files in OST -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0

[JIRA] (OVIRT-1455) Deep dive about STD-CI
by Barak Korren (oVirt JIRA) 18 Jun '17

18 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1455?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1455: ----------------------------------- Assignee: Barak Korren (was: infra) > Deep dive about STD-CI > ---------------------- > > Key: OVIRT-1455 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1455 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: standard-ci > > Not enough people understand standard-CI and mock-runner. > Lets make a deep-dive to teach people. -- This message was sent by Atlassian JIRA (v1000.1068.0#100050)

1 0