- Infra - oVirt List Archives

[JIRA] (OVIRT-881) prepare for bugizlla 5 upgrade - api changes
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-881?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-881: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) > prepare for bugizlla 5 upgrade - api changes > -------------------------------------------- > > Key: OVIRT-881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-881 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > Priority: High > > oVirt Bugzilla will be upgraded to Bugzilla 5.0 in the following months, > We should make sure all our automation still works with the new API and verify mostly Gerrit Hooks still works. > Also, the new version will include RESTAPI as oppose to XMLRPC which was used until now. > Worth looking for existing tools / SDKs which exists that we might be able to use. > cc [~amarchuk] [~sbendavi(a)redhat.com] [~ederevea] -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0

new default jenkins monitoring view for unstable jobs
by Eyal Edri 14 Dec '16

14 Dec '16

FYI, To improve our monitoring and response on critical jobs that affect the whole infra ( i.e system jobs, publishers,etc...) I've changed the default view to include only jobs from: - experimental flows - system jobs - publishers - system jobs ( cleaners, etc...) This will help infra team track and fix wide infra issues much faster. All other 'check-merged' jobs should be monitored by the relevant maintainers, same as check-patch jobs. On any issue found that fail due to infra, the flow should be opening a ticket to infra-support(a)ovirt.org or on jira.ovirt.org. This will help us as a team to be alert on important things and handle tickets for failing jobs due to infra issues in a more structured and orderly way. -- 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)

1 0

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

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] Greg Sheremeta commented on OVIRT-904: -------------------------------------- We can move it. How about we move it to ovirt's infra when we upgrade to patternfly3, which will happen for oVirt 4.2? I can name the rpm "ovirt-patternfly3". I'll need some help figuring out how to put it in the ovirt static repo. > 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.621.2#100023)

1 0

[JIRA] (OVIRT-817) Install notification plugin for jenkins.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-817?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-817: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Install notification plugin for jenkins.ovirt.org > ------------------------------------------------- > > Key: OVIRT-817 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-817 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > please follow https://ovirt-jenkins.getbadges.io/manager/project/2924/app/5820/show -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0

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

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-904: -------------------------------------------- Blocked By: pending response from requestor Status: Blocked (was: To Do) > 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.621.2#100023)

1 0

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

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-904: ------------------------------------------------- What was the decision? Can you move the patternfly to ovirt static repo? > 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.621.2#100023)

1 0

[JIRA] (OVIRT-910) mock_runner.sh seems to run slower on newer slaves
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-910?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-910: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) I think its duplicate of the 10-50 min task, feel free to close duplicate if its the case. > 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: Evgheni Dereveanchin > > 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/cache/mock -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0

[JIRA] (OVIRT-918) upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ]
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-918: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ] > -------------------------------------------------------------------------------------------------------- > > Key: OVIRT-918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-918 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Allon Mureinik > Assignee: Evgheni Dereveanchin > > If a subject of a change has special characters, they get HTML-encoded when presenting it in the Jenkins manual trigger job. > See screenshot for an example: > http://imgur.com/G1M7vNu -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0

[JIRA] (OVIRT-918) upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ]
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-918?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-918: -------------------------------------------- Summary: upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ] (was: Special characters escaped in Jenkins manual triggering of CI) > upgrade Gerrit Trigger plugin to latest [Special characters escaped in Jenkins manual triggering of CI ] > -------------------------------------------------------------------------------------------------------- > > Key: OVIRT-918 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-918 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Allon Mureinik > Assignee: infra > > If a subject of a change has special characters, they get HTML-encoded when presenting it in the Jenkins manual trigger job. > See screenshot for an example: > http://imgur.com/G1M7vNu -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
by eyal edri [Administrator] (oVirt JIRA) 14 Dec '16

14 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-935?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-935: ------------------------------------------------- [~bkorren(a)redhat.com] [~sbonazolla(a)redhat.com] thoughts? we might wait a long time until the bug is fixed. > Unable to build fc25 chroots with mock > -------------------------------------- > > Key: OVIRT-935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Nadav Goldin > Assignee: infra > > Mock fails when trying to build the chroot for fedora25, on installing '@buildsys-build' group(with dnf) stage. > Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781 > Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file. > Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always install 'libcrypt' first. > Until fixed this will block us from building anything with mock on fc25(hit it when trying to build fc25 RPMs for lago). > Error logs: > {code} > DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/', '--releasever', '25', 'install', '@buildsys-build', 'git', 'python', 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', > .... > DEBUG util.py:421: Yum command has been deprecated, use dnf instead. > DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. > DEBUG util.py:421: Error: libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64 > DEBUG util.py:421: Error: libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64 > DEBUG util.py:421: You could try using --skip-broken to work around the problem > DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest > DEBUG util.py:557: Child return code was: 1 > DEBUG util.py:180: kill orphans > {code} -- This message was sent by Atlassian JIRA (v1000.621.2#100023)

1 0