- Infra - oVirt List Archives

[CQ]: 83841, 24 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '17

20 Nov '17

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

1 0

[JIRA] (OVIRT-1775) system-sync_mirrors-fedora-updates-fc25-x86_64 job sometimes takes 3+ hours to complete
by Evgheni Dereveanchin (oVirt JIRA) 20 Nov '17

20 Nov '17

This is a multi-part message in MIME format... ------------=_1511217421-12837-375 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1775: ------------------------------------------- Summary: system-sync_mirrors-fedora-updates-fc25-x86_64 job sometimes takes 3+ hours to complete Key: OVIRT-1775 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1775 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt Infra Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low The fc25 mirror sync job takes hours to complete: http://jenkins.ovirt.org/view/All%20Running%20jobs/job/system-sync_mirrors-… Builds #801, #813, #822, #825, #831, #839 took more than 3 hours to complete. Looking at the mirror server during build #839, reposync and genpkgmetadata.py processes were consuming resources and constantly waiting in D state with I/O Wait being around 70% Opening a ticket to investigate the root cause of this slowdown. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072) ------------=_1511217421-12837-375 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1775:</h3> <pre> Summary: system-sync_mirrors-fedora-updates-fc25-x86_64 job sometimes takes 3+ hours to complete Key: OVIRT-1775 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1775 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt Infra Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low</pre> <p>The fc25 mirror sync job takes hours to complete: <a href="http://jenkins.ovirt.org/view/All%20Running%20jobs/job/system-sync_mirrors-…">http://jenkins.ovirt.org/view/All%20Running%20jobs/job/system-sync_mirrors-…</a></p> <p>Builds #801, #813, #822, #825, #831, #839 took more than 3 hours to complete. Looking at the mirror server during build #839, reposync and genpkgmetadata.py processes were consuming resources and constantly waiting in D state with I/O Wait being around 70%</p> <p>Opening a ticket to investigate the root cause of this slowdown.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511217421-12837-375--

1 0

[CQ]: 83300, 28 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '17

20 Nov '17

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

1 0

[CQ]: 84382, 3 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '17

20 Nov '17

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

1 0

[CQ]: 84346, 4 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 20 Nov '17

20 Nov '17

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

1 0

[JIRA] (OVIRT-1709) provision Persistent Storage for OpenShift
by Evgheni Dereveanchin (oVirt JIRA) 20 Nov '17

20 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1709?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1709: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > provision Persistent Storage for OpenShift > ------------------------------------------ > > Key: OVIRT-1709 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1709 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OpenShift > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > Labels: openshift > > The OpenShift instance in PHX currently does not have any Persistent Storage assigned to it which is needed for things like databases and other important data. Opening this ticket to track how many volumes we may need and attach them. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)

1 0

[CQ]: 84379,1 (vdsm-jsonrpc-java) failed "ovirt-4.1" system tests
by oVirt Jenkins 20 Nov '17

20 Nov '17

Change 84379,1 (vdsm-jsonrpc-java) is probably the reason behind recent system test failures in the "ovirt-4.1" 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/84379/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1350/

1 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package
by eyal edri (oVirt JIRA) 20 Nov '17

20 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-886: ---------------------------- Status: To Do (was: In Progress) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)

1 0

[JIRA] (OVIRT-1774) Upstream source collector can fail to push on multi-branch projects
by Barak Korren (oVirt JIRA) 20 Nov '17

20 Nov '17

This is a multi-part message in MIME format... ------------=_1511186869-30492-188 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1774?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1774: -------------------------------- Epic Link: OVIRT-400 > Upstream source collector can fail to push on multi-branch projects > ------------------------------------------------------------------- > > Key: OVIRT-1774 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: poll-upstream-sources, upstream-source-collector > > When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the '{{upstream-sources.yaml}}' file, regardless of the branch they may belong to. > The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed. > The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072) ------------=_1511186869-30492-188 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1774?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1774:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Upstream source collector can fail to push on multi-branch projects</h3> <pre> Key: OVIRT-1774 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: poll-upstream-sources, upstream-source-collector</pre> <p>When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the ‘{{upstream-sources.yaml}}’ file, regardless of the branch they may belong to. The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed. The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511186869-30492-188--

1 0

[JIRA] (OVIRT-1774) Upstream source collector can fail to push on multi-branch projects
by Barak Korren (oVirt JIRA) 20 Nov '17

20 Nov '17

This is a multi-part message in MIME format... ------------=_1511186815-19288-176 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1774: ----------------------------------- Summary: Upstream source collector can fail to push on multi-branch projects Key: OVIRT-1774 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the '{{upstream-sources.yaml}}' file, regardless of the branch they may belong to. The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed. The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072) ------------=_1511186815-19288-176 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1774:</h3> <pre> Summary: Upstream source collector can fail to push on multi-branch projects Key: OVIRT-1774 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1774 Project: oVirt - virtualization made easy Issue Type: Bug Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>When the upstream source collection code looks for similar patches in order to avoid pushing a new patch, it lookes for patches that contain the same change to the ‘{{upstream-sources.yaml}}’ file, regardless of the branch they may belong to.</p> <p>The code currently ignores the possibility that similar changes might be required for different branches, in which case different patches may need to be pushed.</p> <p>The way of detecting similar patches should be changed so that either the branch name is included in the checksum that are used to identify a patch, or the query is limited to patches of the branch being handled.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100072)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyz…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1511186815-19288-176--

1 0