December 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-910: ------------------------------- Epic Link: OVIRT-400 > mock_runner.sh seems to run slower on newer slaves > -------------------------------------------------- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on /var/lib/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-910: ------------------------------------ [~ederevea], [~amarchuk] any idea what we can do to improve this? > mock_runner.sh seems to run slower on newer slaves > -------------------------------------------------- > > Key: OVIRT-910 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. > I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. > I suspect this may be because the older slaves have a different FS mounted on /var/lib/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
by Barak Korren (oVirt JIRA) 06 Dec '16

06 Dec '16

Barak Korren created OVIRT-910: ---------------------------------- Summary: mock_runner.sh seems to run slower on newer slaves Key: OVIRT-910 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-910 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Reporter: Barak Korren Assignee: infra After implementing speedup improvements for mock_runner.sh (Specifically enabling it to deploy the chroot by extracting a tarball as opposed to installing it with yum every time), I started monitoring run times for vdsm check_patch jobs. I've noticed that jobs that are running on the old slaves (fc24-vm*) seem to initialize mock faster then ones running on new slaves (vm*) - 17seconds vs 57 seconds respectively. I suspect this may be because the older slaves have a different FS mounted on /var/lib/mock -- This message was sent by Atlassian JIRA (v1000.610.2#100023)

1 0

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

06 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-909?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-909: ------------------------------------ Hmm... I can make an educated guess that what we're seeing here is that some files in the local git clone belong to the root user as opposed to the jenkins user. This could happen if something from inside mock is running any git commands that write to the repo... I guess what we could do is make mock_cleanup.sh ensure that no file are left in $WORKSPACE that do not belong the 'jenkins' > 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-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