- Infra - oVirt List Archives

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-904: ------------------------------------------------- [~sbonazolla@redhat.com][~mperina][~gshereme@redhat.com] is it possible to get pattenfly from other place than Copr? We're seeing more and more failures on repos hosted by copr, we might want to find a more stable repo on other services. Who is building/maintaining those builds? > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-904: ------------------------------------ Which projects are coming from Copr? Maybe they would like us to host their artifacts on resources.ovirt.org (And would happily make their CI systems update it with new builds)? Or perhaps they would push into Fedora? or EPEL? or CentOS? Or even just GitHub? I guess if we setup out own mirrors for stuff it will solve our problems, but a project that only releases on copr has a problem IMO.... > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by Evgheni Dereveanchin (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-904: -------------------------------------------- I do not think there are mirrors for COPR as its content changes too often and isn't used by a lot of people. > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-904: ------------------------------------------------- This won't prevent it from failing in the future. [~ederevea] is it possible to add more mirrors here as you did for std ci? > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4285 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 06 Dec '16

06 Dec '16

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4285/, Build Number: 4285, Build Status: SUCCESS

1 0

[JIRA] (OVIRT-909) Several git errors in several jobs
by eyal edri [Administrator] (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-909: ------------------------------------------------- [~ederevea] I think you have another ticket on it, need to find it, but as it continuous to happen on multiple jobs, please give it high priority, We can do a more aggressive cleanup before git clone or shutdown problematic slaves if it happens only on specific ones, but let's address it now even with the cost of adding a few more seconds to runtime until we have a proper solution. > Several git errors in several jobs > ---------------------------------- > > Key: OVIRT-909 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > > The following jobs all had the same git issue, first cloning then cleaning: > * * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… > * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… > * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… > This happened several times in the last weeks. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-909) Several git errors in several jobs
by Fabian Deutsch (oVirt JIRA) 06 Dec '16

06 Dec '16

Fabian Deutsch created OVIRT-909: ------------------------------------ Summary: Several git errors in several jobs Key: OVIRT-909 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-909 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Fabian Deutsch Assignee: infra Priority: Highest The following jobs all had the same git issue, first cloning then cleaning: * * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… * http://jenkins.ovirt.org/user/fabiand/my-views/view/Unstable/job/ovirt-node… This happened several times in the last weeks. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-908) jenkins failures
by eyal edri [Administrator] (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-908: ------------------------------------------------- What makes you think its false positives? We need to look at the logs ( which I can't see in the build, and needs to be fixed ). On Tue, Dec 6, 2016 at 1:02 PM, Martin Polednik (oVirt JIRA) < -- 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) > jenkins failures > ---------------- > > Key: OVIRT-908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: infra > > Hi, > after pushing update to my patch series[1], I've been greeted with > unhealthy amount of jenkins failures. Actually, it's a single fail > that affected all but one(!) patch. > The failure: ERROR: Command failed. See logs for output. [2] > Can we get these issues solved or have some > false-positive/false-negative protection (preferably both)? > [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching > [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/conso… > Regards, > mpolednik -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-908) jenkins failures
by eyal edri [Administrator] (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-908: ------------------------------------------------- [~sbendavi(a)redhat.com] please check why the jobs isn't archiving logs and then we need to see what the error was to determine if its false or not. > jenkins failures > ---------------- > > Key: OVIRT-908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: infra > > Hi, > after pushing update to my patch series[1], I've been greeted with > unhealthy amount of jenkins failures. Actually, it's a single fail > that affected all but one(!) patch. > The failure: ERROR: Command failed. See logs for output. [2] > Can we get these issues solved or have some > false-positive/false-negative protection (preferably both)? > [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching > [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/conso… > Regards, > mpolednik -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-908) jenkins failures
by Martin Polednik (oVirt JIRA) 06 Dec '16

06 Dec '16

Martin Polednik created OVIRT-908: ------------------------------------- Summary: jenkins failures Key: OVIRT-908 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Martin Polednik Assignee: infra Hi, after pushing update to my patch series[1], I've been greeted with unhealthy amount of jenkins failures. Actually, it's a single fail that affected all but one(!) patch. The failure: ERROR: Command failed. See logs for output. [2] Can we get these issues solved or have some false-positive/false-negative protection (preferably both)? [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/conso… Regards, mpolednik -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1

[JIRA] (OVIRT-907) Add CI for mock_runner.sh
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-907?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-907: ------------------------------- Epic Link: OVIRT-400 > Add CI for mock_runner.sh > ------------------------- > > Key: OVIRT-907 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-907 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > We have some CI jobs running on our "Jenkins" repo right now. Those jobs mostly check YAML, but they are also useful for checking changes to mock_runner.sh because they are running inside it. However: > # These jobs do a full YAML check even when it is not needed. > # We're not actually checking mock_runner.sh for all the platforms it simulates. > We've already seem some regressions happen in the CI system because we don't have enough tests for mock_runner.sh > This ticket is for creating good CI coverage for mock_runner.sh, all that is needed to be done in practice is make some changes to the check_patch.sh script and the YAML so that: > * YAML checking is skipped if no JJB-related changes were done > * Various features of mock_runner like the installation of packages for the *.packages files are checked. > * The tests are ran for all platforms that mock_runner.sh supports. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-907) Add CI for mock_runner.sh
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

Barak Korren created OVIRT-907: ---------------------------------- Summary: Add CI for mock_runner.sh Key: OVIRT-907 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-907 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra We have some CI jobs running on our "Jenkins" repo right now. Those jobs mostly check YAML, but they are also useful for checking changes to mock_runner.sh because they are running inside it. However: # These jobs do a full YAML check even when it is not needed. # We're not actually checking mock_runner.sh for all the platforms it simulates. We've already seem some regressions happen in the CI system because we don't have enough tests for mock_runner.sh This ticket is for creating good CI coverage for mock_runner.sh, all that is needed to be done in practice is make some changes to the check_patch.sh script and the YAML so that: * YAML checking is skipped if no JJB-related changes were done * Various features of mock_runner like the installation of packages for the *.packages files are checked. * The tests are ran for all platforms that mock_runner.sh supports. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

Re: engine 3.6 build fails
by Barak Korren 06 Dec '16

06 Dec '16

On 6 December 2016 at 10:16, Barak Korren <bkorren(a)redhat.com> wrote: >> >> I think that the issue could be related to this change: >> https://gerrit.ovirt.org/#/c/67801 >> >> adding Barak > > Hmm... yes my bad... it has to do with the el6 chroots using > "groupsinstall" to setup things instead of "install"... I'll try to > see if I can work around that... (I'm thinking I can get away with > moving el6 to use "install" b/c the 'yum' doing the setup is the one > on the host which should be el7 or newer) Here, this should fix this: https://gerrit.ovirt.org/#/c/67860/ Lets merge it quickly (and then I'll have to erase the mock cache on the slave to get the chroot rebuilt) One more thing - please make sure to address such emails to infra as well next time so other infra members know what is going on... -- Barak Korren bkorren(a)redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/

1 1

[JIRA] (OVIRT-906) Permissions to new user
by Shlomo Ben David (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-906?page=com.atlassian.jira.p… ] Shlomo Ben David reassigned OVIRT-906: -------------------------------------- Assignee: Shlomo Ben David (was: infra) > Permissions to new user > ----------------------- > > Key: OVIRT-906 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Benny Zlotnik > Assignee: Shlomo Ben David > > Hi, > Please grant my Jenkins user (bzlotnik) the dev permissions > Thanks! -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-906) Permissions to new user
by Shlomo Ben David (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-906?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-906: ---------------------------------------- Hi Benny, I added your user to the dev role in Jenkins. Please sign out and sign back into Jenkins to apply the new role. Best Regards, Shlomi Ben-David | DevOps Engineer | Red Hat ISRAEL RHCSA | RHCE IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci) OPEN SOURCE - 1 4 011 && 011 4 1 On Tue, Dec 6, 2016 at 10:44 AM, Benny Zlotnik (oVirt JIRA) < > Permissions to new user > ----------------------- > > Key: OVIRT-906 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Benny Zlotnik > Assignee: infra > > Hi, > Please grant my Jenkins user (bzlotnik) the dev permissions > Thanks! -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-906) Permissions to new user
by Benny Zlotnik (oVirt JIRA) 06 Dec '16

06 Dec '16

Benny Zlotnik created OVIRT-906: ----------------------------------- Summary: Permissions to new user Key: OVIRT-906 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-906 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Benny Zlotnik Assignee: infra Hi, Please grant my Jenkins user (bzlotnik) the dev permissions Thanks! -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1

[oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3389 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 06 Dec '16

06 Dec '16

------=_Part_2_1254376304.1481012231762 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3389/, Build Number: 3389, Build Status: FAILURE ------=_Part_2_1254376304.1481012231762--

1 1

Permissions for the manual trigger
by Benny Zlotnik 06 Dec '16

06 Dec '16

Hi, I am new in the oVirt storage team and I am getting this error: "bzlotnik is missing the Gerrit/ManualTrigger permission" Can anyone please grant me the permission? My username is bzlotnik Thanks!

2 1

[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves
by Nadav Goldin (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-905?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-905: ------------------------------------ No problem to change it, think it is just old left-overs, we test fc24 anyways. > lago_master_check jobs still require fc23 slaves > ------------------------------------------------ > > Key: OVIRT-905 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL in a couple of weeks we need to check if we can change this to newer Fedora versions or CentOS -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

oVirt infra daily report - unstable production jobs - 159
by jenkins＠jenkins.phx.ovirt.org 06 Dec '16

06 Dec '16

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/159//artifact/exported-a… Cheers, Jenkins

1 0

[JIRA] (OVIRT-905) lago_master_check jobs still require fc23 slaves
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '16

05 Dec '16

Evgheni Dereveanchin created OVIRT-905: ------------------------------------------ Summary: lago_master_check jobs still require fc23 slaves Key: OVIRT-905 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-905 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Lago check jobs require "nested && fc23" labels, and as Fedora 23 will be EOL in a couple of weeks we need to check if we can change this to newer Fedora versions or CentOS -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

planned jenkins restart
by Evgheni Dereveanchin 05 Dec '16

05 Dec '16

Hi everyone, I am going to restart Jenkins in order to update several plugins. No new builds will be scheduled during this maintenance period. I will announce you once it is finished. Regards, Evgheni Dereveanchin

1 1

[oVirt Jenkins] test-repo_ovirt_experimental_3.6 - Build #4269 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 05 Dec '16

05 Dec '16

------=_Part_279_1329297632.1480959216790 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/4269/, Build Number: 4269, Build Status: SUCCESS ------=_Part_279_1329297632.1480959216790--

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by Shlomo Ben David (oVirt JIRA) 05 Dec '16

05 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-904: ---------------------------------------- [~eedri] currently I don't see any problem with the [1] repository 1. The old jobs from 2/12/2016 that were failed, do not exist 2. The latest jobs successfully passed [1] - http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-870) Access to artifactory.ovirt.org is slow
by eyal edri [Administrator] (oVirt JIRA) 05 Dec '16

05 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-870?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-870: -------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > Access to artifactory.ovirt.org is slow > --------------------------------------- > > Key: OVIRT-870 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-870 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Juan Hernández > Assignee: infra > > Access to artifactory.ovirt.org seems to be very slow now. For example, > in the following build: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_check-patch-fc24… > It is responding with a transfer rate of 0.2 KiB per second: > Downloaded: > http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/apache/maven/plug… > (7 KB at 0.2 KB/sec) > Can this be improved? > -- > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > 3ºD, 28016 Madrid, Spain > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-870) Access to artifactory.ovirt.org is slow
by Gil Shinar (oVirt JIRA) 05 Dec '16

05 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-870?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-870: ---------------------------------- This build is very old. It had succeeded many times since then. I suggest to close this ticket. > Access to artifactory.ovirt.org is slow > --------------------------------------- > > Key: OVIRT-870 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-870 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Juan Hernández > Assignee: infra > > Access to artifactory.ovirt.org seems to be very slow now. For example, > in the following build: > http://jenkins.ovirt.org/job/ovirt-engine-api-model_master_check-patch-fc24… > It is responding with a transfer rate of 0.2 KiB per second: > Downloaded: > http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/apache/maven/plug… > (7 KB at 0.2 KB/sec) > Can this be improved? > -- > Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta > 3ºD, 28016 Madrid, Spain > Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3927 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 05 Dec '16

05 Dec '16

------=_Part_277_2056239299.1480939320068 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3927/, Build Number: 3927, Build Status: SUCCESS ------=_Part_277_2056239299.1480939320068--

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 05 Dec '16

05 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-904: ------------------------------------------------- [~sbendavi(a)redhat.com] [~ederevea] can we do something about it? maybe add more mirrors to copr? > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > 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" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by danken (oVirt JIRA) 05 Dec '16

05 Dec '16

danken created OVIRT-904: ---------------------------- Summary: False CI-1 due to unreachable copr-be.cloud.fedoraproject.org Key: OVIRT-904 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: danken Assignee: infra Many patches on https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to failure: repodata/repomd.xml from patternfly: [Errno 256] No more mirrors to try. 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" http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-901) bad mirror caused check-merged jobs to fail
by Gil Shinar (oVirt JIRA) 05 Dec '16

05 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-901?page=com.atlassian.jira.p… ] Gil Shinar commented on OVIRT-901: ---------------------------------- For now, at least for the repo closure job, I have worked around with this patch: https://gerrit.ovirt.org/#/c/67776/ > bad mirror caused check-merged jobs to fail > ------------------------------------------- > > Key: OVIRT-901 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-901 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > > check-merged jobs fails on bad mirrors: > If we can't defend ourselves from repomd.xml file errors, lets setup a mirror when we control the mirror sync and we can decide on the update times ( maybe even disable jenkins jobs when the update is running to avoid errors ) > http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/103/console > 07:35:30 Can't download or revert repomd.xml for check-epel-el7 > 07:35:30 Some dependencies may not be complete for this repository > 07:35:30 Run as root to get all dependencies or use -t to enable a user temp cache > 07:35:30 Checking Dependencies > 07:35:30 failure: repodata/151a911cc4b434fcd135e243eec4a4f1d8c1943595a92e2bb838cda5f03577ff-primary.sqlite.xz from check-epel-el7: [Errno 256] No more mirrors to try. > 07:35:30 http://mirror.switch.ch/ftp/mirror/epel/7/x86_64/repodata/151a911cc4b434fcd…: [Errno 14] HTTP Error 404 - Not Found -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

Build failed in Jenkins: ovirt_master_system-tests #854
by jenkins＠jenkins.phx.ovirt.org 05 Dec '16

05 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_master_system-tests/854/changes> Changes: [Yaniv Kaul] CHAP and IPv6 for iSCSI [Anton Marchukov] Updated Fedora distro list for repoman (-fc23 +fc25) ------------------------------------------ [...truncated 749 lines...] ## Sat Dec 3 02:46:05 UTC 2016 Finished env: el7:epel-7-x86_64 ## took 892 seconds ## rc = 1 ########################################################## ##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv ##! Last 20 log entries: logs/mocker-epel-7-x86_64.el7.basic_suite_master.sh/basic_suite_master.sh.log ##! + env_cleanup + echo '#########################' ######################### + local res=0 + local uuid + echo '======== Cleaning up' ======== Cleaning up + [[ -e <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo '----------- Cleaning with lago' ----------- Cleaning with lago + lago --workdir <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> destroy --yes --all-prefixes + echo '----------- Cleaning with lago done' ----------- Cleaning with lago done + [[ 0 != \0 ]] + echo '======== Cleanup done' ======== Cleanup done + exit 0 + exit Took 746 seconds =================================== ##! ##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ##!######################################################## ########################################################## Build step 'Execute shell' marked build as failure Performing Post build task... Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo 'shell_scripts/system_tests.collect_logs.sh' # # Required jjb vars: # version # VERSION=master SUITE_TYPE= WORKSPACE="$PWD" OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION" TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts" rm -rf "$WORKSPACE/exported-artifacts" mkdir -p "$WORKSPACE/exported-artifacts" if [[ -d "$TESTS_LOGS" ]]; then mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/" fi [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson6244207805446786015.sh + echo shell_scripts/system_tests.collect_logs.sh shell_scripts/system_tests.collect_logs.sh + VERSION=master + SUITE_TYPE= + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + OVIRT_SUITE=master + TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_system-tests/854/artifact/exporte…> + mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests/854/artifact/exporte…> + [[ -d <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + mv <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> <http://jenkins.ovirt.org/job/ovirt_master_system-tests/854/artifact/exporte…> POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Match found for :.* : True Logical operation result is TRUE Running script : #!/bin/bash -xe echo "shell-scripts/mock_cleanup.sh" shopt -s nullglob WORKSPACE="$PWD" # Make clear this is the cleanup, helps reading the jenkins logs cat <<EOC _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### EOC # Archive the logs, we want them anyway logs=( ./*log ./*/logs ) if [[ "$logs" ]]; then for log in "${logs[@]}" do echo "Copying ${log} to exported-artifacts" mv $log exported-artifacts/ done fi # stop any processes running inside the chroot failed=false mock_confs=("$WORKSPACE"/*/mocker*) # Clean current jobs mockroot if any for mock_conf_file in "${mock_confs[@]}"; do [[ "$mock_conf_file" ]] || continue echo "Cleaning up mock $mock_conf" mock_root="${mock_conf_file##*/}" mock_root="${mock_root%.*}" my_mock="/usr/bin/mock" my_mock+=" --configdir=${mock_conf_file%/*}" my_mock+=" --root=${mock_root}" my_mock+=" --resultdir=$WORKSPACE" #TODO: investigate why mock --clean fails to umount certain dirs sometimes, #so we can use it instead of manually doing all this. echo "Killing all mock orphan processes, if any." $my_mock \ --orphanskill \ || { echo "ERROR: Failed to kill orphans on $chroot." failed=true } mock_root="$(\ grep \ -Po "(?<=config_opts\['root'\] = ')[^']*" \ "$mock_conf_file" \ )" || : [[ "$mock_root" ]] || continue mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $chroot. Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true } done done # Clean any leftover chroot from other jobs for mock_root in /var/lib/mock/*; do this_chroot_failed=false mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || : if [[ "$mounts" ]]; then echo "Found mounted dirs inside the chroot $mock_root." \ "Trying to umount." fi for mount in "${mounts[@]}"; do sudo umount --lazy "$mount" \ || { echo "ERROR: Failed to umount $mount." failed=true this_chroot_failed=true } done if ! $this_chroot_failed; then sudo rm -rf "$mock_root" fi done if $failed; then echo "Aborting." exit 1 fi # remove mock system cache, we will setup proxies to do the caching and this # takes lots of space between runs shopt -u nullglob sudo rm -Rf /var/cache/mock/* # restore the permissions in the working dir, as sometimes it leaves files # owned by root and then the 'cleanup workspace' from jenkins job fails to # clean and breaks the jobs sudo chown -R "$USER" "$WORKSPACE" # Drop all left over libvirt domains for UUID in $(virsh list --all --uuid); do virsh destroy $UUID || : sleep 2 virsh undefine --remove-all-storage --storage vda --snapshots-metadata $UUID || : done [ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson7539346291946703264.sh + echo shell-scripts/mock_cleanup.sh shell-scripts/mock_cleanup.sh + shopt -s nullglob + WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> + cat _______________________________________________________________________ ####################################################################### # # # CLEANUP # # # ####################################################################### + logs=(./*log ./*/logs) + [[ -n ./ovirt-system-tests/logs ]] + for log in '"${logs[@]}"' + echo 'Copying ./ovirt-system-tests/logs to exported-artifacts' Copying ./ovirt-system-tests/logs to exported-artifacts + mv ./ovirt-system-tests/logs exported-artifacts/ + failed=false + mock_confs=("$WORKSPACE"/*/mocker*) + for mock_conf_file in '"${mock_confs[@]}"' + [[ -n <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> ]] + echo 'Cleaning up mock ' Cleaning up mock + mock_root=mocker-epel-7-x86_64.el7.cfg + mock_root=mocker-epel-7-x86_64.el7 + my_mock=/usr/bin/mock + my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests'> + my_mock+=' --root=mocker-epel-7-x86_64.el7' + my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/'> + echo 'Killing all mock orphan processes, if any.' Killing all mock orphan processes, if any. + /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> --orphanskill WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test….> Using default... INFO: mock.py version 1.2.21 starting (python version = 3.5.1)... Start: init plugins INFO: selinux enabled Finish: init plugins Start: run Finish: run ++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/ovirt-system-test…> + mock_root=epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + [[ -n epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a ]] + mounts=($(mount | awk '{print $3}' | grep "$mock_root")) ++ mount ++ awk '{print $3}' ++ grep epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + : + [[ -n '' ]] + false + shopt -u nullglob + sudo rm -Rf /var/cache/mock/epel-7-x86_64-4ddbe48c8f8b7d8c2c3635b52313f04a + sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_master_system-tests/ws/> ++ virsh list --all --uuid POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 1 Recording test results Archiving artifacts

1 3

[oVirt Jenkins] system-backup_jenkins_ovirt_org - Build # 224 - Failure!
by jenkins＠jenkins.phx.ovirt.org 05 Dec '16

05 Dec '16

Project: http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/ Build: http://jenkins.ovirt.org/job/system-backup_jenkins_ovirt_org/224/ Build Number: 224 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #224 [Evgheni Dereveanchin] OVIRT-645 remove repoproxy for CentOS 7 x86_64 [Eyal Edri] move basic suite to run only nightly ----------------- Failed Tests: ----------------- No tests ran.

1 6

oVirt infra daily report - unstable production jobs - 158
by jenkins＠jenkins.phx.ovirt.org 05 Dec '16

05 Dec '16

------=_Part_271_237532515.1480892409104 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/158//artifact/exported-a… Cheers, Jenkins ------=_Part_271_237532515.1480892409104 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 - 04/12/2016 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Jobs (Production)</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x…">cockpit-ovirt_ovirt-4.1_build-artifacts-fc23-x86_64</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/fabric-ovirt_master_check-merged-el7-x86_64/">fabric-ovirt_master_check-merged-el7-x86_64</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/ovirt-engine-api-explorer_master_build-artifac…">ovirt-engine-api-explorer_master_build-artifacts-fc23-x86_64</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/ovirt-guest-agent_master_build-artifacts-fc23-…">ovirt-guest-agent_master_build-artifacts-fc23-x86_64</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/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-el7-x86_64</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/ovirt-hosted-engine-ha_master_build-artifacts-…">ovirt-hosted-engine-ha_master_build-artifacts-fc24-x86_64</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/ovirt-live_master_create-iso-el7-x86_64/">ovirt-live_master_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live </h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-el7-x86_6…">ovirt-node-ng_master_build-artifacts-el7-x86_64</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/ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-3.6_build-artifacts-el7-x86_64</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/ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x8…">ovirt-node-ng_ovirt-4.0_build-artifacts-el7-x86_64</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/ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el…">ovirt-node-ng_ovirt-4.1-pre_build-artifacts-el7-x86_64</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/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</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/ovirt-node_ovirt-3.6_create-iso-el7_merged/">ovirt-node_ovirt-3.6_create-iso-el7_merged</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/ovirt-optimizer_4.0_build-artifacts-el6-x86_64/">ovirt-optimizer_4.0_build-artifacts-el6-x86_64</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/ovirt_3.6_he-system-tests/">ovirt_3.6_he-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/ovirt_master_system-tests/">ovirt_master_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/ovirt_master_system-tests_debug/">ovirt_master_system-tests_debug</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/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</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/system-backup_jenkins_ovirt_org/">system-backup_jenkins_ovirt_org</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/vdsm_4.0_check-merged-fc23-x86_64/">vdsm_4.0_check-merged-fc23-x86_64</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/vdsm_master_check-merged-el7-x86_64/">vdsm_master_check-merged-el7-x86_64</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_271_237532515.1480892409104--

1 0

Re: [ovirt-devel] Experimental Flow for Master Fails to Run a VM
by Yaniv Kaul 04 Dec '16

04 Dec '16

On Dec 4, 2016 10:57 PM, "Eyal Edri" <eedri(a)redhat.com> wrote: tests are back to stable, but with a cost of not testing 4.1 CL. DC level. But we are not explicitly using any of the 4.1 features for the time being. (I'd like to believe implictly we did, qcow2v3 for example). Iets hope we get centos 7.3 soon. Indeed - but we also need virt-builder image for it. Y. On Dec 4, 2016 22:41, "Yaniv Kaul" <ykaul(a)redhat.com> wrote: > > > On Dec 4, 2016 6:42 PM, "Arik Hadas" <ahadas(a)redhat.com> wrote: > > Yaniv will try to lower the cluster level used in the system-tests to 4.0 > - this is supposed to solve the issue. > > > Done. > Y. > > If it won't help (we will know it in about an hour), we'll add a db-script > that changes the rng device of the blank template only. > > On Sun, Dec 4, 2016 at 3:34 PM, Eyal Edri <eedri(a)redhat.com> wrote: > >> FYI, >> >> I opened a bug [1] to track this issue since I don't see any attempts to >> resolve the issue on the thread, hopefully a bug will get more attention. >> Opened on VDSM since we see the libvirt error there, feel free to move >> product/team. >> >> >> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1401303 >> >> On Sun, Dec 4, 2016 at 1:23 PM, Eyal Edri <eedri(a)redhat.com> wrote: >> >>> Not sure if relevant, but Juan posted a fix for SDK4 last time it >>> happened ( but different failure on log-collector ): >>> >>> https://gerrit.ovirt.org/#/c/67213/ >>> >>> * Added `urandom` to the `RngSource` enumerated type. >>> >>> On Sun, Dec 4, 2016 at 9:17 AM, Eyal Edri <eedri(a)redhat.com> wrote: >>> >>>> And its still failing from Friday, >>>> Since we don't have official Centos 7.3 repos yet ( hopefully we'll >>>> have it this week, but as of this moment its not published yet ) , we have >>>> to either revert the offending patch >>>> or send a quick fix. >>>> >>>> Right now all experimental flows for master are not working and nightly >>>> rpms are not refreshed with new RPMs. >>>> >>>> >>>> >>>> On Fri, Dec 2, 2016 at 9:41 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: >>>> >>>>> >>>>> >>>>> On Dec 2, 2016 2:11 PM, "Anton Marchukov" <amarchuk(a)redhat.com> wrote: >>>>> >>>>> Hello Martin. >>>>> >>>>> Do by outdated you mean the old libvirt? If so that is that livirt >>>>> available in CentOS 7.2? There is no 7.3 yet. >>>>> >>>>> >>>>> Right, this is the issue. >>>>> Y. >>>>> >>>>> >>>>> Anton. >>>>> >>>>> On Fri, Dec 2, 2016 at 1:07 PM, Martin Polednik <mpolednik(a)redhat.com> >>>>> wrote: >>>>> >>>>>> On 02/12/16 10:55 +0100, Anton Marchukov wrote: >>>>>> >>>>>>> Hello All. >>>>>>> >>>>>>> Engine log can be viewed here: >>>>>>> >>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >>>>>>> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >>>>>>> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >>>>>>> _basic_sanity.py/lago-basic-suite-master-engine/_var_log_ovi >>>>>>> rt-engine/engine.log >>>>>>> >>>>>>> I see the following exception there: >>>>>>> >>>>>>> 2016-12-02 04:29:24,030-05 DEBUG >>>>>>> [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >>>>>>> (ResponseWorker) [83b6b5d] Message received: {"jsonrpc": "2.0", "id": >>>>>>> "ec254aad-441b-47e7-a644-aebddcc1d62c", "result": true} >>>>>>> 2016-12-02 04:29:24,030-05 ERROR >>>>>>> [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) >>>>>>> [83b6b5d] Not able to update response for >>>>>>> "ec254aad-441b-47e7-a644-aebddcc1d62c" >>>>>>> 2016-12-02 04:29:24,041-05 DEBUG >>>>>>> [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] >>>>>>> (DefaultQuartzScheduler3) [47a31d72] Rescheduling >>>>>>> DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.ref >>>>>>> reshLightWeightData#-9223372036854775775 >>>>>>> as there is no unfired trigger. >>>>>>> 2016-12-02 04:29:24,024-05 DEBUG >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Exception: >>>>>>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>>>>>> VDSGenericException: VDSNetworkException: Timeout during xml-rpc call >>>>>>> at org.ovirt.engine.core.vdsbroke >>>>>>> r.vdsbroker.FutureVDSCommand.get(FutureVDSCommand.java:73) >>>>>>> [vdsbroker.jar:] >>>>>>> >>>>>>> ... >>>>>>> >>>>>>> 2016-12-02 04:29:24,042-05 ERROR >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Timeout waiting for >>>>>>> VDSM response: Internal timeout occured >>>>>>> 2016-12-02 04:29:24,044-05 DEBUG >>>>>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVD >>>>>>> SCommand] >>>>>>> (default task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] START, >>>>>>> GetCapabilitiesVDSCommand(HostName = lago-basic-suite-master-host0, >>>>>>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', >>>>>>> hostId='5eb7019e-28a3-4f93-9188-685b6c64a2f5', >>>>>>> vds='Host[lago-basic-suite-master-host0,5eb7019e-28a3-4f93-9 >>>>>>> 188-685b6c64a2f5]'}), >>>>>>> log id: 58f448b8 >>>>>>> 2016-12-02 04:29:24,044-05 DEBUG >>>>>>> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (default >>>>>>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] SEND >>>>>>> destination:jms.topic.vdsm_requests >>>>>>> reply-to:jms.topic.vdsm_responses >>>>>>> content-length:105 >>>>>>> >>>>>>> >>>>>>> Please note that this runs on localhost with local bridge. So it is >>>>>>> not >>>>>>> likely to be network itself. >>>>>>> >>>>>> >>>>>> The main issue I see is that the VM run command has actually failed >>>>>> due to libvirt no accepting /dev/urandom as RNG source[1]. This was >>>>>> done as engine patch and according to git log, posted around Mon Nov >>>>>> 28. Also adding Jakub - this should either not happen from engine's >>>>>> point of view or the lago host is outdated. >>>>>> >>>>>> [1] >>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >>>>>> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >>>>>> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >>>>>> _basic_sanity.py/lago-basic-suite-master-host0/_var_log_vdsm/vdsm.log >>>>>> >>>>>> >>>>>> Anton. >>>>>>> >>>>>>> On Fri, Dec 2, 2016 at 10:43 AM, Anton Marchukov < >>>>>>> amarchuk(a)redhat.com> >>>>>>> wrote: >>>>>>> >>>>>>> FYI. Experimental flow for master currently fails to run a VM. The >>>>>>>> tests >>>>>>>> times out while waiting for 180 seconds: >>>>>>>> >>>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ >>>>>>>> master/3838/testReport/(root)/004_basic_sanity/vm_run/ >>>>>>>> >>>>>>>> This is reproducible over 23 runs of this happened tonight, sounds >>>>>>>> like a >>>>>>>> regression to me: >>>>>>>> >>>>>>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/ >>>>>>>> >>>>>>>> I will update here with additional information once I find it. >>>>>>>> >>>>>>>> Last successful run was with this patch: >>>>>>>> >>>>>>>> https://gerrit.ovirt.org/#/c/66416/ (vdsm: API: move vm parameters >>>>>>>> fixup >>>>>>>> in a method) >>>>>>>> >>>>>>>> Known to start failing around this patch: >>>>>>>> >>>>>>>> https://gerrit.ovirt.org/#/c/67647/ (vdsmapi: fix a typo in string >>>>>>>> formatting) >>>>>>>> >>>>>>>> Please notes that we do not have gating implemented yet, so >>>>>>>> everything >>>>>>>> that was merged in between those patches might have caused this (not >>>>>>>> necessary in vdsm project). >>>>>>>> >>>>>>>> Anton. >>>>>>>> -- >>>>>>>> Anton Marchukov >>>>>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Anton Marchukov >>>>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>>> Devel mailing list >>>>>>> Devel(a)ovirt.org >>>>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Anton Marchukov >>>>> Senior Software Engineer - RHEV CI - Red Hat >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> Devel(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Devel mailing list >>>>> Devel(a)ovirt.org >>>>> http://lists.ovirt.org/mailman/listinfo/devel >>>>> >>>> >>>> >>>> >>>> -- >>>> 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) >>>> >>> >>> >>> >>> -- >>> 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) >>> >> >> >> >> -- >> 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) >> >> _______________________________________________ >> Devel mailing list >> Devel(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/devel >> > > >

1 0

Re: [ovirt-devel] Experimental Flow for Master Fails to Run a VM
by Eyal Edri 04 Dec '16

04 Dec '16

And its still failing from Friday, Since we don't have official Centos 7.3 repos yet ( hopefully we'll have it this week, but as of this moment its not published yet ) , we have to either revert the offending patch or send a quick fix. Right now all experimental flows for master are not working and nightly rpms are not refreshed with new RPMs. On Fri, Dec 2, 2016 at 9:41 PM, Yaniv Kaul <ykaul(a)redhat.com> wrote: > > > On Dec 2, 2016 2:11 PM, "Anton Marchukov" <amarchuk(a)redhat.com> wrote: > > Hello Martin. > > Do by outdated you mean the old libvirt? If so that is that livirt > available in CentOS 7.2? There is no 7.3 yet. > > > Right, this is the issue. > Y. > > > Anton. > > On Fri, Dec 2, 2016 at 1:07 PM, Martin Polednik <mpolednik(a)redhat.com> > wrote: > >> On 02/12/16 10:55 +0100, Anton Marchukov wrote: >> >>> Hello All. >>> >>> Engine log can be viewed here: >>> >>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >>> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >>> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >>> _basic_sanity.py/lago-basic-suite-master-engine/_var_log_ovi >>> rt-engine/engine.log >>> >>> I see the following exception there: >>> >>> 2016-12-02 04:29:24,030-05 DEBUG >>> [org.ovirt.vdsm.jsonrpc.client.internal.ResponseWorker] >>> (ResponseWorker) [83b6b5d] Message received: {"jsonrpc": "2.0", "id": >>> "ec254aad-441b-47e7-a644-aebddcc1d62c", "result": true} >>> 2016-12-02 04:29:24,030-05 ERROR >>> [org.ovirt.vdsm.jsonrpc.client.JsonRpcClient] (ResponseWorker) >>> [83b6b5d] Not able to update response for >>> "ec254aad-441b-47e7-a644-aebddcc1d62c" >>> 2016-12-02 04:29:24,041-05 DEBUG >>> [org.ovirt.engine.core.utils.timer.FixedDelayJobListener] >>> (DefaultQuartzScheduler3) [47a31d72] Rescheduling >>> DEFAULT.org.ovirt.engine.core.bll.gluster.GlusterSyncJob.ref >>> reshLightWeightData#-9223372036854775775 >>> as there is no unfired trigger. >>> 2016-12-02 04:29:24,024-05 DEBUG >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Exception: >>> org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: >>> VDSGenericException: VDSNetworkException: Timeout during xml-rpc call >>> at org.ovirt.engine.core.vdsbroker.vdsbroker.FutureVDSCommand.g >>> et(FutureVDSCommand.java:73) >>> [vdsbroker.jar:] >>> >>> ... >>> >>> 2016-12-02 04:29:24,042-05 ERROR >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.PollVDSCommand] (default >>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] Timeout waiting for >>> VDSM response: Internal timeout occured >>> 2016-12-02 04:29:24,044-05 DEBUG >>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] >>> (default task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] START, >>> GetCapabilitiesVDSCommand(HostName = lago-basic-suite-master-host0, >>> VdsIdAndVdsVDSCommandParametersBase:{runAsync='true', >>> hostId='5eb7019e-28a3-4f93-9188-685b6c64a2f5', >>> vds='Host[lago-basic-suite-master-host0,5eb7019e-28a3-4f93-9 >>> 188-685b6c64a2f5]'}), >>> log id: 58f448b8 >>> 2016-12-02 04:29:24,044-05 DEBUG >>> [org.ovirt.vdsm.jsonrpc.client.reactors.stomp.impl.Message] (default >>> task-12) [d932871a-af4f-4fc9-9ee5-f7a0126a7b85] SEND >>> destination:jms.topic.vdsm_requests >>> reply-to:jms.topic.vdsm_responses >>> content-length:105 >>> >>> >>> Please note that this runs on localhost with local bridge. So it is not >>> likely to be network itself. >>> >> >> The main issue I see is that the VM run command has actually failed >> due to libvirt no accepting /dev/urandom as RNG source[1]. This was >> done as engine patch and according to git log, posted around Mon Nov >> 28. Also adding Jakub - this should either not happen from engine's >> point of view or the lago host is outdated. >> >> [1] >> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ma >> ster/3838/artifact/exported-artifacts/basic_suite_master.sh- >> el7/exported-artifacts/test_logs/basic-suite-master/post-004 >> _basic_sanity.py/lago-basic-suite-master-host0/_var_log_vdsm/vdsm.log >> >> >> Anton. >>> >>> On Fri, Dec 2, 2016 at 10:43 AM, Anton Marchukov <amarchuk(a)redhat.com> >>> wrote: >>> >>> FYI. Experimental flow for master currently fails to run a VM. The tests >>>> times out while waiting for 180 seconds: >>>> >>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ >>>> master/3838/testReport/(root)/004_basic_sanity/vm_run/ >>>> >>>> This is reproducible over 23 runs of this happened tonight, sounds like >>>> a >>>> regression to me: >>>> >>>> http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/ >>>> >>>> I will update here with additional information once I find it. >>>> >>>> Last successful run was with this patch: >>>> >>>> https://gerrit.ovirt.org/#/c/66416/ (vdsm: API: move vm parameters >>>> fixup >>>> in a method) >>>> >>>> Known to start failing around this patch: >>>> >>>> https://gerrit.ovirt.org/#/c/67647/ (vdsmapi: fix a typo in string >>>> formatting) >>>> >>>> Please notes that we do not have gating implemented yet, so everything >>>> that was merged in between those patches might have caused this (not >>>> necessary in vdsm project). >>>> >>>> Anton. >>>> -- >>>> Anton Marchukov >>>> Senior Software Engineer - RHEV CI - Red Hat >>>> >>>> >>>> >>> >>> -- >>> Anton Marchukov >>> Senior Software Engineer - RHEV CI - Red Hat >>> >> >> _______________________________________________ >>> Devel mailing list >>> Devel(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/devel >>> >> >> > > > -- > Anton Marchukov > Senior Software Engineer - RHEV CI - Red Hat > > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > > > > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- 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)

3 5

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3816 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

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

1 94

Build failed in Jenkins: ovirt_master_publish-rpms_nightly #348
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/348/> ------------------------------------------ Started by user Gil Shinar [EnvInject] - Loading node environment variables. Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson3740535846473544521.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/ws/artifacts> Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-el7-x86_64" build number 23 Copied 6 artifacts from "ovirt-host-deploy_master_build-artifacts-fc24-x86_64" build number 13 Copied 8 artifacts from "otopi_master_build-artifacts-el7-x86_64" build number 31 Copied 8 artifacts from "otopi_master_build-artifacts-fc24-x86_64" build number 19 Copied 5 artifacts from "ovirt-vmconsole_master_build-artifacts-el7-x86_64" build number 2 Copied 6 artifacts from "ovirt-vmconsole_master_build-artifacts-fc24-x86_64" build number 1 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-el7-x86_64" build number 61 Copied 10 artifacts from "ovirt-imageio_master_build-artifacts-fc24-x86_64" build number 24 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-iso-uploader_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-el7-x86_64" build number 9 Copied 4 artifacts from "ovirt-log-collector_master_build-artifacts-fc24-x86_64" build number 5 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el7-x86_64" build number 23 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-fc24-x86_64" build number 13 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-el7-x86_64_merged" build number 21 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_master_create-rpms-fc24-x86_64_merged" build number 5 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-el7-x86_64_merged" build number 5 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_master_create-rpms-fc24-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-el7-x86_64_merged" build number 4 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_master_create-rpms-fc24-x86_64_merged" build number 3 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-el7-x86_64" build number 31 Copied 4 artifacts from "ovirt-dwh_master_build-artifacts-fc24-x86_64" build number 11 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-el7-x86_64_merged" build number 15 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_master_create-rpms-fc24-x86_64_merged" build number 10 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-el7-x86_64" build number 11 Copied 4 artifacts from "ovirt-setup-lib_master_build-artifacts-fc24-x86_64" build number 7 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-el7-x86_64" build number 42 Copied 4 artifacts from "vdsm-jsonrpc-java_master_build-artifacts-fc24-x86_64" build number 20 Copied 3 artifacts from "ovirt-engine-sdk_master_build-artifacts-el7-x86_64" build number 101 Copied 5 artifacts from "ovirt-engine-sdk_master_build-artifacts-fc24-x86_64" build number 76 Copied 4 artifacts from "python-ovirt-engine-sdk4_master_build-artifacts-el7-x86_64" build number 2 ERROR: Unable to find a build for artifact copy from: python-ovirt-engine-sdk4_master_build-artifacts-fc24-x86_64

1 3

Build failed in Jenkins: ovirt_4.0_publish-rpms_nightly #247
by jenkins＠jenkins.phx.ovirt.org 04 Dec '16

04 Dec '16

See <http://jenkins.ovirt.org/job/ovirt_4.0_publish-rpms_nightly/247/> ------------------------------------------ Started by user Gil Shinar [EnvInject] - Loading node environment variables. Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_4.0_publish-rpms_nightly/ws/> [WS-CLEANUP] Deleting project workspace... [workspace] $ /bin/bash -xe /tmp/hudson7362465232987529782.sh + rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_publish-rpms_nightly/ws/artifacts> + mkdir <http://jenkins.ovirt.org/job/ovirt_4.0_publish-rpms_nightly/ws/artifacts> Copied 6 artifacts from "ovirt-host-deploy_4.0_build-artifacts-el7-x86_64" build number 17 Copied 6 artifacts from "ovirt-host-deploy_4.0_build-artifacts-fc23-x86_64" build number 17 Copied 8 artifacts from "otopi_4.0_build-artifacts-el7-x86_64" build number 14 Copied 8 artifacts from "otopi_4.0_build-artifacts-fc23-x86_64" build number 13 Copied 6 artifacts from "ovirt-vmconsole_4.0_build-artifacts-el7-x86_64" build number 1 Copied 6 artifacts from "ovirt-vmconsole_4.0_build-artifacts-fc23-x86_64" build number 1 Copied 10 artifacts from "ovirt-imageio_4.0_build-artifacts-el7-x86_64" build number 33 Copied 10 artifacts from "ovirt-imageio_4.0_build-artifacts-fc23-x86_64" build number 34 Copied 4 artifacts from "ovirt-iso-uploader_4.0_build-artifacts-el7-x86_64" build number 11 Copied 4 artifacts from "ovirt-iso-uploader_4.0_build-artifacts-fc23-x86_64" build number 11 Copied 4 artifacts from "ovirt-log-collector_4.0_build-artifacts-el7-x86_64" build number 7 Copied 4 artifacts from "ovirt-log-collector_4.0_build-artifacts-fc23-x86_64" build number 8 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el7-x86_64" build number 23 Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-fc23-x86_64" build number 23 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_4.0_create-rpms-el7-x86_64_merged" build number 8 Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_4.0_create-rpms-fc23-x86_64_merged" build number 8 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_4.0_create-rpms-el7-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-aaa-misc_4.0_create-rpms-fc23-x86_64_merged" build number 1 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_4.0_create-rpms-el7-x86_64_merged" build number 3 Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_4.0_create-rpms-fc23-x86_64_merged" build number 3 Copied 4 artifacts from "ovirt-dwh_4.0_build-artifacts-el7-x86_64" build number 22 Copied 4 artifacts from "ovirt-dwh_4.0_build-artifacts-fc23-x86_64" build number 22 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_4.0_create-rpms-el7-x86_64_merged" build number 10 Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_4.0_create-rpms-fc23-x86_64_merged" build number 10 Copied 3 artifacts from "ovirt-setup-lib_4.0_build-artifacts-el7-x86_64" build number 5 Copied 3 artifacts from "ovirt-setup-lib_4.0_build-artifacts-fc23-x86_64" build number 4 Copied 5 artifacts from "vdsm-jsonrpc-java_4.0_build-artifacts-el7-x86_64" build number 21 Copied 5 artifacts from "vdsm-jsonrpc-java_4.0_build-artifacts-fc23-x86_64" build number 21 Copied 24 artifacts from "ovirt-engine_4.0_build-artifacts-el7-x86_64" build number 1707 Copied 24 artifacts from "ovirt-engine_4.0_build-artifacts-fc23-x86_64" build number 1699 Copied 6 artifacts from "ovirt-engine-sdk_4.0_build-artifacts-el7-x86_64" build number 72 Copied 8 artifacts from "ovirt-engine-sdk_4.0_build-artifacts-fc23-x86_64" build number 75 Copied 3 artifacts from "ovirt-engine-sdk-java_4.0_build-artifacts-el7-x86_64" build number 66 Copied 3 artifacts from "ovirt-engine-sdk-java_4.0_build-artifacts-fc23-x86_64" build number 74 Copied 6 artifacts from "python-ovirt-engine-sdk4_4.0_build-artifacts-el7-x86_64" build number 2 ERROR: Unable to find a build for artifact copy from: python-ovirt-engine-sdk4_4.0_build-artifacts-fc23-x86_64

1 2

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- [~sbendavi(a)redhat.com] can you check if rebasing on someone else patch and pushing again requires the 'forget identity' permission or its a different one? > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by ybronhei (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] ybronhei commented on OVIRT-900: -------------------------------- you can always ignore the patchset and push your version again. otherwise you cant rebase your patch on it I think On Sun, Dec 4, 2016 at 3:00 PM, eyal edri [Administrator] (oVirt JIRA) < -- *Yaniv Bronhaim.* > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- So what you're saying is any 'registered user' should have 'forge author identity' permission? Isn't that a bit of a security issue? On Sun, Dec 4, 2016 at 2:58 PM, ybronhei (oVirt JIRA) < -- 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) > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by ybronhei (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] ybronhei commented on OVIRT-900: -------------------------------- no.. this is not the issue here. I don't try to merge, I try to push a change on a patch that im not the author of it. everyone should allow to do so On Sun, Dec 4, 2016 at 1:25 PM, eyal edri [Administrator] (oVirt JIRA) < -- *Yaniv Bronhaim.* > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- OK, so as I suggested its best to verify the list of people in those groups and add/remove people who are missing. > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1

[JIRA] (OVIRT-902) Speed up mock_runner.sh setup time by using caches.
by Barak Korren (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-902?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-902: ---------------------------------- Assignee: Barak Korren (was: infra) > Speed up mock_runner.sh setup time by using caches. > --------------------------------------------------- > > Key: OVIRT-902 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-902 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > Labels: mock, mock_runner.sh, standard-ci > > We've already known that setting up mock takes a while, but mock has some built-in caching features that should allow us to speed this up. > We need to ensure those features are enabled by mock_runner.sh. The mock options to look at are: > * root_cache_enable > * yum_cache_enable > Both these options should be set to true in the mock chroot config file. > We've been using these option downstream in minimead and the vdsm build scripts, so they should be safe to use. -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-900) Re: Rebase over other author's patch cannot be pushed to gerrit
by Shlomo Ben David (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] Shlomo Ben David commented on OVIRT-900: ---------------------------------------- Only the 'vdsm-master-maintainers' group have full permissions on the master branch (and 'vdsm-maintainers' group as the owner of the project) The user has permission as a registered user: push, verify, code-review on the 'master' branch because he is not a member of that group. > Re: Rebase over other author's patch cannot be pushed to gerrit > --------------------------------------------------------------- > > Key: OVIRT-900 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-900 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Barak Korren > Assignee: Shlomo Ben David > > Forwarding to infra-support. > On 1 December 2016 at 18:03, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > Not sure since when it was changed, but I noticed that I can't push patches > > if I'm not the author > > > > Counting objects: 50, done. > > Delta compression using up to 4 threads. > > Compressing objects: 100% (50/50), done. > > Writing objects: 100% (50/50), 36.66 KiB | 0 bytes/s, done. > > Total 50 (delta 34), reused 0 (delta 0) > > remote: Resolving deltas: 100% (34/34) > > remote: Processing changes: refs: 1, done > > remote: > > remote: ERROR: In commit db14ec7c1555a9eb37a0fb931bbb4ebdfc674bb4 > > remote: ERROR: author email address rnachimu(a)redhat.com > > remote: ERROR: does not match your user account. > > remote: ERROR: > > remote: ERROR: The following addresses are currently registered: > > remote: ERROR: bronhaim(a)gmail.com > > remote: ERROR: ybronhei(a)redhat.com > > remote: ERROR: > > remote: ERROR: To register an email address, please visit: > > remote: ERROR: https://gerrit.ovirt.org/#/settings/contact > > remote: > > remote: > > To ssh://ybronhei@gerrit.ovirt.org:29418/vdsm > > ! [remote rejected] HEAD -> refs/for/master (invalid author) > > error: failed to push some refs to > > 'ssh://ybronhei@gerrit.ovirt.org:29418/vdsm' > > > > We must have permissions to do that, this is part of the rebasing part, and > > I think its fine to fix patches on behalf of someone else.. but its not the > > best practice for reviewing. > > anyway, please undo this change, unless its something that related only to > > my env.. let me know > > > > Thanks > > > > -- > > Yaniv Bronhaim. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-903: ------------------------------------------------- Also, you might want to change the ticket name for " fixing/updating upgrade job" the current title is misleading On Sun, Dec 4, 2016 at 1:11 PM, eyal edri [Administrator] (oVirt JIRA) < -- 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) > master-to-master CI upgrade tests > --------------------------------- > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-903: ------------------------------------------------- well, depending on the amount of effort needed to update the job, we might want to wait with it until the jobs are moved to an ost suit, which is in progress. On Dec 4, 2016 13:07, "Yedidyah Bar David" <didi(a)redhat.com> wrote: On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=23805#comment-23805 ] from-master_el7_merged/ Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra > master-to-master CI upgrade tests > --------------------------------- > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1

Re: [JIRA] (OVIRT-903) master-to-master CI upgrade tests
by Eyal Edri 04 Dec '16

04 Dec '16

well, depending on the amount of effort needed to update the job, we might want to wait with it until the jobs are moved to an ost suit, which is in progress. On Dec 4, 2016 13:07, "Yedidyah Bar David" <didi(a)redhat.com> wrote: On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt JIRA) <jira(a)ovirt-jira.atlassian.net> wrote: > > [ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com. atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=23805#comment-23805 ] > > eyal edri [Administrator] commented on OVIRT-903: > ------------------------------------------------- > > We have master->master upgrade job: > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade- from-master_el7_merged/ Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

1 0

[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by Yedidyah Bar David (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.p… ] Yedidyah Bar David commented on OVIRT-903: ------------------------------------------ On Sun, Dec 4, 2016 at 11:06 AM, eyal edri [Administrator] (oVirt Indeed, and I explained in the ticket why it's not enough as-is. Best, -- Didi > master-to-master CI upgrade tests > --------------------------------- > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA) 04 Dec '16

04 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-903: ------------------------------------------------- We have master->master upgrade job: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… > master-to-master CI upgrade tests > --------------------------------- > > Key: OVIRT-903 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > Recently a patch to the engine [1] added a new package, > with a certain set of dependencies, which broke upgrade. > This is similar to [2] but for a new package. > CI wasn't affected, I think because of [3]. > To make CI test such flows, we should have a job that: > 1. Builds, installs and sets up the version we want to test > 2. Pushes a dummy change to the local git repo (to force > a new version), build the patched tree, create a yum repo > with the build and add it to yum.repos.d. > 3. yum update > 4. engine-setup > Another option is to revert [3], or to duplicate - have > both "upgrade current to self" and "upgrade latest snapshot > to current". The downside is that it will be checked later > than above plan - instead of in the same build, will only > be tested in the first build that uses the snapshot after > it was updated, and also will be misleading, as the reason > why that job failed will not be apparent (which was why > [3] was added). > Please handle. I can of course try to help. Best, > [1] https://gerrit.ovirt.org/66999 > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249 > [3] https://gerrit.ovirt.org/67263 > -- > Didi -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

2 1