November 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2585) Jenkins web is not responsive
by Emil Natan (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2585?page=com.atlassian.jira.… ] Emil Natan commented on OVIRT-2585: ----------------------------------- Duplicates https://ovirt-jira.atlassian.net/browse/OVIRT-2586 > Jenkins web is not responsive > ----------------------------- > > Key: OVIRT-2585 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2585 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2585) Jenkins web is not responsive
by Eyal Edri (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2585?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2585: ---------------------------------- [~ena(a)redhat.com] might be a duplicate also. > Jenkins web is not responsive > ----------------------------- > > Key: OVIRT-2585 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2585 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Edward Haas > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[CQ]: 95645, 1 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Nov '18

25 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95645,1 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 95640,1 (ovirt-dwh) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95640,1 (ovirt-dwh) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95645/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95640/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11494/

1 0

[JIRA] (OVIRT-2584) Jenkins master UI very slow
by Emil Natan (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2584?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2584: ------------------------------ Resolution: Duplicate Status: Done (was: To Do) > Jenkins master UI very slow > --------------------------- > > Key: OVIRT-2584 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2584 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master > Reporter: Emil Natan > Assignee: infra > Priority: Highest > > Jenkins master UI is very slow, sometimes reaching the timeout of the proxy before getting the page. > Looking at the machine I see the CPU utilization ~85-90%. It happened for 2 days in a row (21-22/11). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2584) Jenkins master UI very slow
by Emil Natan (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2584?page=com.atlassian.jira.… ] Emil Natan commented on OVIRT-2584: ----------------------------------- Duplicate of https://ovirt-jira.atlassian.net/browse/OVIRT-2586. Closing this one. > Jenkins master UI very slow > --------------------------- > > Key: OVIRT-2584 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2584 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins Master > Reporter: Emil Natan > Assignee: infra > Priority: Highest > > Jenkins master UI is very slow, sometimes reaching the timeout of the proxy before getting the page. > Looking at the machine I see the CPU utilization ~85-90%. It happened for 2 days in a row (21-22/11). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100095)

1 0

[JIRA] (OVIRT-2586) Jenkins terribly slow and unresponsive
by Emil Natan (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Emil Natan commented on OVIRT-2586: ----------------------------------- This is duplicate of OVIRT-2584, but I'll leave this one open and close OVIRT-2584. On a side note I'm surprised that hotadding CPUs worked, I tried to do the same on jenkins-staging running on the same system, but the added CPUs did not show up (/proc/cpuinfo) until I rebooted the vm. > 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: infra > 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 Emil Natan (oVirt JIRA) 25 Nov '18

25 Nov '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2586?page=com.atlassian.jira.… ] Emil Natan updated OVIRT-2586: ------------------------------ Priority: Highest (was: Medium) > 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: infra > 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

[CQ]: 95644, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Nov '18

25 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95644,1 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 95637,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95637,1 (ovirt-engine-metrics) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95644/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95637/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11488/

1 0

[CQ]: 95643, 2 (ovirt-dwh) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Nov '18

25 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95643,2 (ovirt-dwh) failed. However, this change seems not to be the root cause for this failure. Change 95640,1 (ovirt-dwh) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95640,1 (ovirt-dwh) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95643/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95640/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11482/

1 0

[CQ]: 95642, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Nov '18

25 Nov '18

A system test invoked by the "ovirt-master" change queue including change 95642,1 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 95637,1 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 95637,1 (ovirt-engine-metrics) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/95642/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/95637/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/11476/

1 0