- Infra - oVirt List Archives

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-753: -------------------------------------------- Status: Blocked (was: In Progress) > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-923) define process to manage and apply ansible playbooks
by Evgheni Dereveanchin (oVirt JIRA) 08 Dec '16

08 Dec '16

Evgheni Dereveanchin created OVIRT-923: ------------------------------------------ Summary: define process to manage and apply ansible playbooks Key: OVIRT-923 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-923 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low We already have a repository with ansible code, but to use it effectively we need to define a way to manage playbooks and run them effectively. As Ansible Tower is not open source we need to investigate other solutions on the market. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-913) Speed up mock with the `nosync` package
by Barak Korren (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-913?page=com.atlassian.jira.p… ] Barak Korren reassigned OVIRT-913: ---------------------------------- Assignee: Barak Korren (was: infra) > Speed up mock with the `nosync` package > --------------------------------------- > > Key: OVIRT-913 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-913 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Labels: mock, mock_runner.sh, standard-ci > > The {{nosync}} package can make mock faster by making it ignore all {{sync(2)}} calls. > {{mock_runner.sh}} actually already enables this setting in the chroot configuration files, but it cannot work without the package. > We need to check if this actually makes mock faster, and if so, add it to the slaves. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-226?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-226: -------------------------------------------- Priority: Lowest (was: Medium) > Add new checks to ovirt-system-test to ensure no sensitive data leak in logs > ---------------------------------------------------------------------------- > > Key: OVIRT-226 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: sbonazzo > Assignee: infra > Priority: Lowest > > Original request is on bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1118354 > Not sure how to implement the test using jenkins. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-449) Add junit report to ovirt-engine standard ci
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-449?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-449: -------------------------------------------- Priority: Low (was: Medium) > Add junit report to ovirt-engine standard ci > -------------------------------------------- > > Key: OVIRT-449 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-449 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: David Caro Estevez > Assignee: infra > Priority: Low > > Currently there are to ways of doing it: > * Using a special job template for ovirt-engine (easy to do now, hard to maintain/reuse) > * Using jenkins pipeline plugin to dynamically add it to any job that generates a report (hard to do right now, easy to maintain/reuse) -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

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

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-900?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-900: ------------------------------------------------- [~ybronhei(a)redhat.com] can you check if it works for you now? > 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.620.0#100023)

1 0

[JIRA] (OVIRT-705) Upgrade to puppet 4.0
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-705?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-705: -------------------------------------------- Priority: Lowest (was: Medium) > Upgrade to puppet 4.0 > --------------------- > > Key: OVIRT-705 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-705 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Lowest > > Related to the migration of foreman + puppet master to PHX, and worth its own ticket. > Will be addressed once we have a new foreman 1.12 up & running. > Also, nice blog on the migration might be useful: > http://hggh.github.io/puppet/debian/2016/08/19/puppet-4.x.html -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-729) Jenkins leaves behind connections in ESTABLISHED state
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-729?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-729: ----------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) see if this is still relevant. > Jenkins leaves behind connections in ESTABLISHED state > ------------------------------------------------------ > > Key: OVIRT-729 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-729 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > Throughout the last days I noticed several times when a slave got non-responsive and after rebooting it never recovered until being removed/re-added to Jenkins. > Further investigation on el7-vm06.phx.ovirt.org revealed that on Jenkins the connection is still marked as "ESTABLISHED" hours after the slave crashed and rebooted: > {quote} > tcp6 0 0 66.187.230.92:33374 66.187.230.77:22 ESTABLISHED 14625/java > {quote} > Due to this new SSH connections are not opened and Jenkins can't reconnect to the slave. > I didn't see this behavior before, maybe it is related to the latest security upgrade of jenkins. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-453) Gerrit: Issue 3885: Failed to index change
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-453?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-453: -------------------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) Havn't seen this another time since the upgrade. We'll do a periodic upgrade to 2.13/2.14 which will anyway include a fix for this. the upgrade will be monitored on another ticket. > Gerrit: Issue 3885: Failed to index change > ------------------------------------------ > > Key: OVIRT-453 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-453 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > Its an open issue [1] in Gerrit, but still no fix available. > We'll track it and see if there is a pending fix, cc'ing infra-support to > open a ticket to track this. > [1] > https://code.google.com/p/gerrit/issues/detail?can=2&start=0&num=100&q=&col… > On Sun, Mar 27, 2016 at 7:03 AM, Nadav Goldin <ngoldin(a)redhat.com> wrote: > > Hi, > > gerrit started throwing weird errors this morning, such as: > > > >> internal server error: com.google.gerrit.server.git.UpdateException: > >> java.io.IOException: java.util.concurrent.ExecutionException: > >> org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed) > >> > > > > restarting it now. > > > > > > Nadav. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHEV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-296) [jenkins] take offline faulty bad slaves
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-296?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-296: -------------------------------------------- Priority: Medium (was: Highest) > [jenkins] take offline faulty bad slaves > ---------------------------------------- > > Key: OVIRT-296 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-296 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: jenkins, monitoring, > > it seems that quite often we hit an issue with a specific slave on phx, due to various reasons (out of space/git/network/etc..). > which leads to multiple jobs trying to run on it and failing. > we need an automated way of finding this. > proposal: > add post groovy build to jobs that will take a slave offline if it's misbehaves using: > manager.build.getBuiltOn().toComputer.setTemporarilyOffline(true) > the trick is to find such a slave and to be able to know if it failed consistently in the past X hours to justify it's disable. > we need some sort of counter or service to track slaves and thier error state and according to it take offline a specific slave. > for example: > if a slave was failing x jobs in Y time and runtime was < Z min , it might indicate such a problem. > (e.g 10 jobs were failing on the same slave in a timeframe of 5 min and job runtime was less than a 1 min.. ) > the post script should email infra(a)ovirt.org that it disabled a slave and we should look into it. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0