- Infra - oVirt List Archives

oVirt infra daily report - unstable production jobs - 1070
by jenkins＠jenkins.phx.ovirt.org 15 Jan '20

15 Jan '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/1070//artifact/exported… Cheers, Jenkins

1 0

planned Jenkins restart
by Evgheni Dereveanchin 14 Jan '20

14 Jan '20

Hi everyone, I'll be performing a planned Jenkins restart within the next hour. No new jobs will be scheduled during this maintenance period. I will inform you once it is back online. -- Regards, Evgheni Dereveanchin

1 1

[CQ]: 106086, 3 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '20

14 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106086,3 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) 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 106120,5 (ovirt-system-tests) 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/106086/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2795/

1 0

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

14 Jan '20

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

1 0

[CQ]: 106298, 1 (ovirt-system-tests) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 14 Jan '20

14 Jan '20

A system test invoked by the "ovirt-4.3" change queue including change 106298,1 (ovirt-system-tests) failed. However, this change seems not to be the root cause for this failure. Change 106120,5 (ovirt-system-tests) 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 106120,5 (ovirt-system-tests) 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/106298/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/2794/

1 0

[CQ]: 106120, 5 (ovirt-system-tests) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 106120,5 (ovirt-system-tests) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/106120/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18021/

1 0

Missing e-mail notifications from gerrit about review requests
by Milan Zamazal 14 Jan '20

14 Jan '20

Hi, it seems gerrit doesn't send e-mail notifications to reviewers when they are added as reviewers to patches. For example, I haven't received an e-mail notification about being added as a reviewer to https://gerrit.ovirt.org/106310 and https://gerrit.ovirt.org/106311 today. I have heard from Tomasz that he has this problem for a couple of last days (at least since Friday) too. Other e-mail notifications from gerrit seem to come normally. Could you please check what's wrong? Thanks, Milan

1 0

[CQ]: 105979,5 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 14 Jan '20

14 Jan '20

Change 105979,5 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/105979/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/18014/

1 0

[JIRA] (OVIRT-2857) zone transfer to OSAS dns broken from PHX
by Evgheni Dereveanchin (oVirt JIRA) 14 Jan '20

14 Jan '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2857?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2857: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > zone transfer to OSAS dns broken from PHX > ----------------------------------------- > > Key: OVIRT-2857 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2857 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Marc Dequènes (Duck) > > I've been experiencing issues with hostnames showing outdated IPs recently in PHX. > Looks like zone transfer is broken between foreman.phx.ovirt.org and OSAS DNS servers, specifically ns1.osci.io and ns2.osci.io that are mentioned as authoritative for this zone. > Example: > dig staging-shift-int.phx.ovirt.org @foreman.phx.ovirt.org > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 38.145.50.70 > dig staging-shift-int.phx.ovirt.org @ns1.osci.io > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 > dig staging-shift-int.phx.ovirt.org @ns2.osci.io > ;; ANSWER SECTION: > staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 > The correct IP is 38.145.50.70 in this case and the name server in PHX has already been restarted and re-transfer initiated several times yet unfortunately the changes are not visible on OSAS DNS which is blocking us from rebuilding the staging OpenShift environment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0

[JIRA] (OVIRT-2857) zone transfer to OSAS dns broken from PHX
by Evgheni Dereveanchin (oVirt JIRA) 14 Jan '20

14 Jan '20

Evgheni Dereveanchin created OVIRT-2857: ------------------------------------------- Summary: zone transfer to OSAS dns broken from PHX Key: OVIRT-2857 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2857 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I've been experiencing issues with hostnames showing outdated IPs recently in PHX. Looks like zone transfer is broken between foreman.phx.ovirt.org and OSAS DNS servers, specifically ns1.osci.io and ns2.osci.io that are mentioned as authoritative for this zone. Example: dig staging-shift-int.phx.ovirt.org @foreman.phx.ovirt.org ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 38.145.50.70 dig staging-shift-int.phx.ovirt.org @ns1.osci.io ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 dig staging-shift-int.phx.ovirt.org @ns2.osci.io ;; ANSWER SECTION: staging-shift-int.phx.ovirt.org. 86400 IN A 66.187.230.36 The correct IP is 38.145.50.70 in this case and the name server in PHX has already been restarted and re-transfer initiated several times yet unfortunately the changes are not visible on OSAS DNS which is blocking us from rebuilding the staging OpenShift environment. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100118)

1 0