February 2020 - Infra - oVirt List Archives

[CQ]: 106678, 12 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Feb '20

26 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106678,12 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106678/12 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/20622/

1 0

[JIRA] (OVIRT-2868) Please update all jenkins slaves
by Anton Marchukov (oVirt JIRA) 26 Feb '20

26 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2868?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2868: -------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Please update all jenkins slaves > -------------------------------- > > Key: OVIRT-2868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2868 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Slaves > Reporter: Sandro Bonazzola > Assignee: Evgheni Dereveanchin > Priority: High > > Jenkins el7 slaves are running 5 months old kernel missing security updates and features causing CQ failures. > due to features expected to work at cpu level and enabled only by a mix of kernel and microcode_ctl updates. > Please update and reboot all slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121)

1 0

[CQ]: 106613, 14 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Feb '20

26 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106613,14 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106613/14 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/20615/

1 0

[CQ]: 106594, 12 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 26 Feb '20

26 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106594,12 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106594/12 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/20608/

1 0

oVirt infra daily report - unstable production jobs - 1112
by jenkins＠jenkins.phx.ovirt.org 26 Feb '20

26 Feb '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1112//artifact/exported… Cheers, Jenkins

1 0

[JIRA] (OVIRT-2868) Please update all jenkins slaves
by Sandro Bonazzola (oVirt JIRA) 25 Feb '20

25 Feb '20

Sandro Bonazzola created OVIRT-2868: --------------------------------------- Summary: Please update all jenkins slaves Key: OVIRT-2868 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2868 Project: oVirt - virtualization made easy Issue Type: Task Components: Jenkins Slaves Reporter: Sandro Bonazzola Assignee: infra Priority: High Jenkins el7 slaves are running 5 months old kernel missing security updates and features causing CQ failures. due to features expected to work at cpu level and enabled only by a mix of kernel and microcode_ctl updates. Please update and reboot all slaves. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121)

1 0

[CQ]: 106543, 11 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 25 Feb '20

25 Feb '20

A system test invoked by the "ovirt-master" change queue including change 106543,11 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 106280,6 (vdsm) 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 106280,6 (vdsm) 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/106543/11 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106280/6 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/20601/

1 0

Too many open files in system (was: [oVirt Jenkins] ovirt-system-tests_he-basic-suite-4.3 - Build # 361 - Still Failing!)
by Yedidyah Bar David 25 Feb '20

25 Feb '20

On Tue, Feb 25, 2020 at 3:59 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/ > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-4.3/361/ This one failed with "Too many open files in system" (appears 30 times in console log, failing many different things). > Build Number: 361 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #360 > [Lucia Jelinkova] Added UI test for vGPU dialog > > [Evgheni Dereveanchin] Specify TLS secret name for letsencrypt-acme > > [Barak Korren] stdci-tools: Automate container build > > [Gal Ben Haim] global-setup: Configure known_hosts > > [Gal Ben Haim] Run global setup and then checkout the repo > > [Daniel Belenky] git_utils: add function to initialize git repo > > [Daniel Belenky] Introduce file_utils library > > > Changes for Build #361 > [Michal Skrivanek] add python3-websocket-client > > [Gal Ben Haim] Add coverage to OST container slaves > > [Barak Korren] stdci.yaml: ost-container only in check-patch > > [Gal Ben Haim] Make sure that ssh dir exists > > [Barak Korren] global_setup.sh: Small whitespace fix > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. -- Didi

2 1

[JIRA] (OVIRT-2867) OpenShift nodes NotReady: PLEG is not healthy
by Evgheni Dereveanchin (oVirt JIRA) 25 Feb '20

25 Feb '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2867?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2867: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > OpenShift nodes NotReady: PLEG is not healthy > --------------------------------------------- > > Key: OVIRT-2867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2867 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > Several OpenShift bare metals in PHX are marked as NotReady with "PLEG not healthy" errors: > origin-node[38916]: I0225 13:13:56.574031 38916 kubelet.go:1779] skipping pod synchronization - [PLEG is not healthy: pleg was last seen active 4h14m43.440447302s ago; threshold is 3m0s] > Need to confirm the reason since this destabilizes the CI system and decreases its capacity. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121)

1 0

[JIRA] (OVIRT-2867) OpenShift nodes NotReady: PLEG is not healthy
by Evgheni Dereveanchin (oVirt JIRA) 25 Feb '20

25 Feb '20

Evgheni Dereveanchin created OVIRT-2867: ------------------------------------------- Summary: OpenShift nodes NotReady: PLEG is not healthy Key: OVIRT-2867 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2867 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Priority: High Several OpenShift bare metals in PHX are marked as NotReady with "PLEG not healthy" errors: origin-node[38916]: I0225 13:13:56.574031 38916 kubelet.go:1779] skipping pod synchronization - [PLEG is not healthy: pleg was last seen active 4h14m43.440447302s ago; threshold is 3m0s] Need to confirm the reason since this destabilizes the CI system and decreases its capacity. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121)

1 0