- Infra - oVirt List Archives

Planned restart of production services
by Evgheni Dereveanchin 21 Dec '17

21 Dec '17

Hi everyone, I will be restarting several production systems today to perform planned maintenance. The following services may be unreachable for some period of time: - gerrit.ovirt.org - code review - jenkins.ovirt.org - CI master It will not be possible to submit/review patches, clone repositories or run CI jobs during this period. I will announce you once the maintenance is complete. -- Regards, Evgheni Dereveanchin

1 1

[JIRA] (OVIRT-1813) unexpected IP change of the gerrit
by Evgheni Dereveanchin (oVirt JIRA) 21 Dec '17

21 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1813?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1813: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > unexpected IP change of the gerrit > ---------------------------------- > > Key: OVIRT-1813 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1813 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Gerrit/git > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Highest > > During maintenance work the Gerrit system lost its AWS elastic IP and I cannot assign it back. I changed DNS mappings and we may need to update SPF to allow email sending to mitigate this -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1813) unexpected IP change of the gerrit
by Evgheni Dereveanchin (oVirt JIRA) 21 Dec '17

21 Dec '17

Evgheni Dereveanchin created OVIRT-1813: ------------------------------------------- Summary: unexpected IP change of the gerrit Key: OVIRT-1813 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1813 Project: oVirt - virtualization made easy Issue Type: Outage Components: Gerrit/git Reporter: Evgheni Dereveanchin Assignee: infra Priority: Highest During maintenance work the Gerrit system lost its AWS elastic IP and I cannot assign it back. I changed DNS mappings and we may need to update SPF to allow email sending to mitigate this -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1812) Gerrit bug check is buggy
by Nir Soffer (oVirt JIRA) 20 Dec '17

20 Dec '17

Nir Soffer created OVIRT-1812: --------------------------------- Summary: Gerrit bug check is buggy Key: OVIRT-1812 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1812 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra Gerrit bug check code is treating unrelated urls as Bug-Url: Patch Set 1: Verified-1 - Check Bug-Url::1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Bug-Url::1527827::OK, classification: 'Red Hat', product: 'Red Hat Enterprise Virtualization Manager' (-1) - Check Product::WARN, failed to get bug info (private bug or bug doesn't exist) - Check TM::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Backport::OK, The patch backported to all the relevant stable branches. - Set POST::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1527827::OK, tracker status: POST The commit message is: commit 1b666da534c50321ada448e4bf397cab0306fcf1 Author: Nir Soffer <nsoffer(a)redhat.com> Date: Tue Dec 5 23:47:24 2017 +0200 fileSD: Use InterruptibleDirectFile backend FileStorgeDomainManifest uses now InterruptibleDirectFile for the external leases backend. This ensure that the process does not become uninterruptible if storage is non-responsive. This change bypass the python bug[1] causing the entire process to hang when opening the special xleases volume. Now the operation is done in the child process outside of Vdsm. [1] https://bugzilla.redhat.com/1520068 Change-Id: I8a0eb42baa73b6c0a877ad9acbe53ac51f31bfea Bug-Url: https://bugzilla.redhat.com/1527827 Signed-off-by: Nir Soffer <nsoffer(a)redhat.com> There is exactly one Bur-Url. The other url is a bugzilla url but it should be consumed only by humans, not by machines. Machines should use only the Bug-Url. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

Gerrit bug check is buggy
by Nir Soffer 20 Dec '17

20 Dec '17

Gerrit bug check code is treating unrelated urls as Bug-Url: Patch Set 1: Verified-1 - Check Bug-Url::1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Bug-Url::1527827::OK, classification: 'Red Hat', product: 'Red Hat Enterprise Virtualization Manager' (-1) - Check Product::WARN, failed to get bug info (private bug or bug doesn't exist) - Check TM::WARN, failed to get bug info (private bug or bug doesn't exist) - Check Backport::OK, The patch backported to all the relevant stable branches. - Set POST::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1520068::WARN, failed to get bug info (private bug or bug doesn't exist) - Update Tracker::#1527827::OK, tracker status: POST The commit message is: commit 1b666da534c50321ada448e4bf397cab0306fcf1 Author: Nir Soffer <nsoffer(a)redhat.com> Date: Tue Dec 5 23:47:24 2017 +0200 fileSD: Use InterruptibleDirectFile backend FileStorgeDomainManifest uses now InterruptibleDirectFile for the external leases backend. This ensure that the process does not become uninterruptible if storage is non-responsive. This change bypass the python bug[1] causing the entire process to hang when opening the special xleases volume. Now the operation is done in the child process outside of Vdsm. [1] https://bugzilla.redhat.com/1520068 Change-Id: I8a0eb42baa73b6c0a877ad9acbe53ac51f31bfea Bug-Url: https://bugzilla.redhat.com/1527827 Signed-off-by: Nir Soffer <nsoffer(a)redhat.com> There is exactly one Bur-Url. The other url is a bugzilla url but it should be consumed only by humans, not by machines. Machines should use only the Bug-Url. Nir

1 0

[CQ]: 85642, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Dec '17

20 Dec '17

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

1 0

[CQ]: 85641, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Dec '17

20 Dec '17

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

1 0

oVirt infra weekly meeting notes 20.12.2017
by Evgheni Dereveanchin 20 Dec '17

20 Dec '17

Hi everyone, Please find the topics of this week's infra meeting below: General updates: - Christmas is approaching, quiet period ahead - oVirt 4.2.0 released <https://www.ovirt.org/release/4.2.0/> PHX DC: - PHX engine is already at RC3 level (same version as 4.2.0 GA) - Staging Jenkins updated, Prod upgrade planned OVIRT-1807 <https://ovirt-jira.atlassian.net/browse/OVIRT-1807> - Staging Gerrit updated, Prod upgrade planned OVIRT-1809 <https://ovirt-jira.atlassian.net/browse/OVIRT-1809> - Jenkins slave configuration migration to global_setup OVIRT-1810 <https://ovirt-jira.atlassian.net/browse/OVIRT-1810> - New mailing list created for managing social network accounts AI: - Check gerrit log rotation in /home/gerrit2 - nothing is deleted, log volume is 538M since 2015 and we do have disk space monitoring set up - Authenticate on Jenkins via Gerrit as SoftwareFactory does it? OVIRT-527 <https://ovirt-jira.atlassian.net/browse/OVIRT-527> -- Regards, Evgheni Dereveanchin

1 0

[CQ]: 85620, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Dec '17

20 Dec '17

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

1 0

[CQ]: 85618, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Dec '17

20 Dec '17

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

1 0