February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1193) add on request 'ci help' command via Gerrit
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1193?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1193: --------------------------------------------- Summary: add on request 'ci help' command via Gerrit (was: Re: Howto message for every gerrit review) > add on request 'ci help' command via Gerrit > ------------------------------------------- > > Key: OVIRT-1193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1193 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > > On 23 February 2017 at 15:10, Martin Sivak <msivak(a)redhat.com> wrote: > > Hi, > > > > do you think it would make sense to send a copy-and-paste ready > > message with help to every new gerrit change? > > > > It could provide all the system test (lago) links, mention the Rerun > > hooks syntax and so on. Just so we do not have to search for it all > > the time? > This is doable, but I think experienced users may find this annoying > it ifs too long. > I'm thinking it may be better to have such a message just suggesting > to type something like '@ci help' to get the full help. > It may even be possible to make it clickable with some trickery rather > then just copy-and-paster ready (I will need to check if its possible > to inject links into Gerrit comments). > Apart from that, Roy offered to write a Gerrit plugin that will add > buttons with the various CI commands. > Adding infra-support to get a Jira ticket opened. > -- > Barak Korren > bkorren(a)redhat.com > RHCE, RHCi, RHV-DevOps Team > https://ifireball.wordpress.com/ -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-987) Infra issues in Jenkins aren't reported properly on most of Jenkins jobs
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-987?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-987: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) > Infra issues in Jenkins aren't reported properly on most of Jenkins jobs > ------------------------------------------------------------------------ > > Key: OVIRT-987 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-987 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: eyal edri [Administrator] > > Findbugs jobs reports an infra problem to gerrit properly: "There was an > infra issue, please contact infra(a)ovirt.org" > It'd be good to have same behavior on the rest of the Jenkins jobs. > Currently there is no differentiation between failure upon an infra issue > and a real patch problem in reporting to gerrit. > Regards, > Yevgeny -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-978) Jenkins slave fails to pull code from gerrit.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-978?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-978: ------------------------------------------------- [~danken(a)redhat.com] we've fixed some issues around fc24 support in CI, do you know if this still failing for you? [~bkorren(a)redhat.com] is this relevant to any known issues we've had recently? > Jenkins slave fails to pull code from gerrit.ovirt.org > ------------------------------------------------------ > > Key: OVIRT-978 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-978 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Occasionally, e.g. > http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/6870/conso… > I see these failures > 07:29:50 Manually triggered by user ishaby(a)redhat.com for Gerrit: > https://gerrit.ovirt.org/68804 > 07:29:50 [EnvInject] - Loading node environment variables. > 07:29:50 Building remotely on fc24-vm15.phx.ovirt.org (fc24 phx > local_disk nested) in workspace > /home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64 > 07:29:50 > git rev-parse --is-inside-work-tree # timeout=10 > 07:29:50 Fetching changes from the remote Git repository > 07:29:50 > git config remote.origin.url > git://gerrit.ovirt.org/vdsm.git # timeout=10 > 07:29:50 Cleaning workspace > 07:29:50 > git rev-parse --verify HEAD # timeout=10 > 07:29:50 Resetting working tree > 07:29:50 > git reset --hard # timeout=10 > 07:29:51 > git clean -fdx # timeout=10 > 07:29:51 Pruning obsolete local branches > 07:29:51 Fetching upstream changes from git://gerrit.ovirt.org/vdsm.git > 07:29:51 > git --version # timeout=10 > 07:29:51 > git -c core.askpass=true fetch --tags --progress > git://gerrit.ovirt.org/vdsm.git refs/changes/04/68804/3 --prune > 07:29:51 ERROR: Error fetching remote repo 'origin' > 07:29:51 hudson.plugins.git.GitException: Failed to fetch from > git://gerrit.ovirt.org/vdsm.git -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-977) puppet does not update packages on fedora slaves
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-977?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-977: ------------------------------------------------- [~ederevea] is this still and issue? > puppet does not update packages on fedora slaves > ------------------------------------------------ > > Key: OVIRT-977 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-977 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Nadav Goldin > Assignee: infra > > Probably related to: https://tickets.puppetlabs.com/browse/PUP-6324 > Using 'latest' does not update the slaves, example: > {code} > Debug: Executing '/usr/bin/yum -d 0 -e 0 -y install mock' > Notice: /Stage[main]/Ovirt_jenkins_slave::Mock_builder/Package[mock]/ensure: ensure changed '1.2.18-1.fc24' to '0:1.2.21-1.fc24' > ... > [root@fc24-vm06 ~]# rpm -qa | grep mock > mock-1.2.18-1.fc24.noarch > {code} > but the actual result of the command is: > {code} > Yum command has been deprecated, redirecting to '/usr/bin/dnf install mock'. > See 'man dnf' and 'man yum2dnf' for more information. > To transfer transaction metadata from yum to DNF, run: > 'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate' > Last metadata expiration check: 0:10:29 ago on Sun Dec 25 12:48:04 2016. > Package mock-1.2.18-1.fc24.noarch is already installed, skipping. > Dependencies resolved. > ============================================================================================================================================================================================================================================== > Package Arch Version Repository Size > ============================================================================================================================================================================================================================================== > Skipping packages with conflicts: > (add '--best --allowerasing' to command line to force their upgrade): > btrfs-progs x86_64 4.5.2-1.fc24 fedora 627 k > distribution-gpg-keys noarch 1.9-1.fc24 updates 127 k > mock noarch 1.2.21-1.fc24 updates 328 k > Transaction Summary > ============================================================================================================================================================================================================================================== > Skip 3 Packages > Nothing to do. > Complete! > {code} > Not saying we should fix this, as: > 1. This is a bug in puppet probably > 2. We're using unsupported puppet version on fedora which we built by our own. > 3. We might prefer to drop puppet for these sort of tasks > But, we should be aware that our puppet infrastructure isn't behaving as expected. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5540 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 26 Feb '17

26 Feb '17

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

1 1

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1084: --------------------------------------------- Epic Link: OVIRT-400 > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1084) Merge github and gerrit jobs
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1084?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1084: --------------------------------------------- Epic Link: OVIRT-400 > Merge github and gerrit jobs > ---------------------------- > > Key: OVIRT-1084 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1084 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Pavel Zhukov > Assignee: infra > Priority: Low > > As per https://ovirt-jira.atlassian.net/browse/OVIRT-970 gerrit and github jobs contan a lot of common code and features so they should be merged and _github_ suffix removed from the job names. -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1109) Create jobs parameter in manual system tests
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1109?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1109: --------------------------------------------- Epic Link: OVIRT-400 > Create jobs parameter in manual system tests > -------------------------------------------- > > Key: OVIRT-1109 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1109 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > You should do that by adding a dynamic parameter that'll have a groovy script such as: > {code} > import jenkins.model.* > def list = [] > def matchedJobs = Jenkins.instance.items.findAll { job -> > job.name =~ /build-artifacts/ > } > matchedJobs.each { job -> > if (!job.name.contains("archived_for_deletion")) { > list << job.name.split('_')[0] > } > } > return list.unique() > {code} > With the above script you'll have all project names. From the project name and the other parameters you can build any job's name: > {code} > {project}_{ovirt_version}_build-artifacts-{distro}-{arch} > {code} -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1109) Create jobs parameter in manual system tests
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1109?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1109: --------------------------------------------- Epic Link: OVIRT-400 > Create jobs parameter in manual system tests > -------------------------------------------- > > Key: OVIRT-1109 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1109 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: infra > > You should do that by adding a dynamic parameter that'll have a groovy script such as: > {code} > import jenkins.model.* > def list = [] > def matchedJobs = Jenkins.instance.items.findAll { job -> > job.name =~ /build-artifacts/ > } > matchedJobs.each { job -> > if (!job.name.contains("archived_for_deletion")) { > list << job.name.split('_')[0] > } > } > return list.unique() > {code} > With the above script you'll have all project names. From the project name and the other parameters you can build any job's name: > {code} > {project}_{ovirt_version}_build-artifacts-{distro}-{arch} > {code} -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0

[JIRA] (OVIRT-1128) Add Jenkins job for testing
by eyal edri [Administrator] (oVirt JIRA) 26 Feb '17

26 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1128?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1128: --------------------------------------------- Labels: staging (was: ) Epic Link: OVIRT-400 can be part of improved jenkins staging with gerrit staging > Add Jenkins job for testing > --------------------------- > > Key: OVIRT-1128 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1128 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Pavel Zhukov > Assignee: infra > Labels: staging > > it'd be good to have jenkins job to test and regenerate jenkins jobs :) > which uses "good" jjb configuration and available for infra team from > any machine. > Currently local JJB instances and configs are used which is not perfect > because configs can be different as well as jjb versions, not rebased > repos can be used for testing Besides of that it requires copying of > configs between machines and so on. > -- > Pavel -- This message was sent by Atlassian JIRA (v1000.784.2#100032)

1 0