December 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2155) remove Jenkins Jabber plugin
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2155?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2155: ---------------------------------------- Issue Type: Sub-task (was: Task) Parent: OVIRT-2612 > remove Jenkins Jabber plugin > ---------------------------- > > Key: OVIRT-2155 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2155 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > We have the jabber-plugin installed (together with instant-messaging it depends on) that does not seem to be used nor do we have any plans to utilize this plugin in the future. > Opening ticket to remove the plugin from the puppet manifest and remove it manually from the Master -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2157) remove Jenkins Copr plugin
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2157?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2157: ---------------------------------------- Issue Type: Sub-task (was: Task) Parent: OVIRT-2612 > remove Jenkins Copr plugin > -------------------------- > > Key: OVIRT-2157 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2157 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > We have the Copr plugin installed on Jenkins and not used by any jobs. > Opening ticket to drop the plugin from the puppet manifest and remove it manually from the Master -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2612) tickets to improve jenkins performance
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

Evgheni Dereveanchin created OVIRT-2612: ------------------------------------------- Summary: tickets to improve jenkins performance Key: OVIRT-2612 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2612 Project: oVirt - virtualization made easy Issue Type: Epic Reporter: Evgheni Dereveanchin Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

Change in barak-test[master]: jenkins integ test
by review＠gerrit-staging.phx.ovirt.org 03 Dec '18

03 Dec '18

From Evgheni Dereveanchin <ederevea(a)redhat.com>: Evgheni Dereveanchin has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/17 ) Change subject: jenkins integ test ...................................................................... Patch Set 1: OVIRT-2606 test -- To view, visit https://gerrit-staging.phx.ovirt.org/17 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I50acc69c8c5b6b3e03f3ced23d72c883ac4db2c2 Gerrit-Change-Number: 17 Gerrit-PatchSet: 1 Gerrit-Owner: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Mon, 03 Dec 2018 16:54:01 +0000 Gerrit-HasComments: No

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2586: ---------------------------------------- Issue Type: Outage (was: By-EMAIL) > Jenkins terribly slow and unresponsive > -------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Priority: Highest > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2586: --------------------------------------------- Here's a memory histogram for top consumers: ||Class||Size (Kb)||% size||Instances||% instances|| |org.jenkinsci.plugins.ssegateway.sse.EventDispatcher$Retry| 4,259,284| 32 |136,297,090 |32 | |java.util.concurrent.ConcurrentLinkedQueue$Node| 3,194,540| 24 |136,300,398 |32 | |java.lang.Object[]| 1,389,218| 10 |25,260,454 |5 | |java.util.ArrayList| 568,681| 4 |24,263,747 |5 | |hudson.plugins.git.Revision| 557,909| 4 |23,804,146 |5 | |java.util.HashMap$Node| 406,807| 3 |13,017,830 |3 | |hudson.plugins.git.util.Build| 372,095| 2 |11,907,066 |2 | |org.eclipse.jgit.lib.ObjectId| 364,458| 2 |11,662,676 |2 | |java.lang.StackTraceElement| 280,683| 2 |8,981,873 |2 | |hudson.plugins.git.Branch| 273,343| 2 |11,662,674 |2 | |char[]| 228,907| 1 |1,744,589 |0 | |byte[]| 145,645| 1 |60,719 |0 | |java.lang.String| 141,084| 1 |6,019,605 |1 | ssegateway is way at the top and it's used by the BlueOcean events API This is not only affecting the UI as it seems but also the tasks that go through the API so we have issues such as OVIRT-2608 for example. > Jenkins terribly slow and unresponsive > -------------------------------------- > > Key: OVIRT-2586 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > Priority: Highest > > Hi, > jenkins is terribly slow and becoming worse every day. > I tried to gain some speed by adding 4 cores to the VM through engine-phx. > It's a bit better but the real issue doesn't seem related to CPU power. > Can anybody investigate? > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 03 Dec '18

03 Dec '18

Failed to run project_setup.sh for: #839 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-9x945.

1 0

[JIRA] (OVIRT-2611) Move "ovirt-srv17" to u/s openshift for testing purposes
by Evgheni Dereveanchin (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2611?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2611: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Move "ovirt-srv17" to u/s openshift for testing purposes > -------------------------------------------------------- > > Key: OVIRT-2611 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2611 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Gal Ben Haim > Assignee: Evgheni Dereveanchin > > Hi, > Please move "ovirt-srv17" from Jenkins to u/s Openshift. For the meanwhile don't add to it the `type: bare-metal` label, since I need it for performance investigation (we want to understand why OST jobs take longer on Openshift). > cc [~dbelenky(a)redhat.com] [~bkorren(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2611) Move "ovirt-srv17" to u/s openshift for testing purposes
by Gal Ben Haim (oVirt JIRA) 03 Dec '18

03 Dec '18

Gal Ben Haim created OVIRT-2611: ----------------------------------- Summary: Move "ovirt-srv17" to u/s openshift for testing purposes Key: OVIRT-2611 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2611 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Gal Ben Haim Assignee: infra Hi, Please move "ovirt-srv17" from Jenkins to u/s Openshift. For the meanwhile don't add to it the `type: bare-metal` label, since I need it for performance investigation (we want to understand why OST jobs take longer on Openshift). cc [~dbelenky(a)redhat.com] [~bkorren(a)redhat.com] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2609) stdci style reports sometimes disappear pretty fast
by Eyal Edri (oVirt JIRA) 03 Dec '18

03 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2609?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2609: ---------------------------------- [~ederevea] what is the current retention policy for builds history? How much can we extend it without affecting performance and space too much? > stdci style reports sometimes disappear pretty fast > --------------------------------------------------- > > Key: OVIRT-2609 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2609 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roman Mohr > Assignee: infra > > Can there be a SLA defined for how long we can see test results until they > get removed? > It does not have to be like on travis (where I can still see all my build > logs from years ago), but at least a predictable period would be nice. The > PR in [1] did for instance not have the results anymore from 5 days ago. > Thanks, > Roman > [1] https://github.com/kubevirt/kubevirt/pull/1744 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0