- Infra - oVirt List Archives

[oVirt Jenkins] standard-enqueue - Build #6906 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 15 Nov '17

15 Nov '17

------=_Part_280_578941169.1510735754629 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/standard-enqueue/6906/ Build Name: #6906 Build Description: Gerrit: 84149 - ovirt-engine-api-metamodel (1.1) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/84149 - title: Update CHANGES.adoc for release 1.1.16 - project: ovirt-engine-api-metamodel - branch: metamodel_1.1 - author: Juan Hernandez <juan.hernandez(a)redhat.com> ------=_Part_280_578941169.1510735754629--

3 6

[JIRA] (OVIRT-1763) Increase entropy for hosts
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510756591-26566-475 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.… ] Barak Korren edited comment on OVIRT-1763 at 11/15/17 2:36 PM: --------------------------------------------------------------- [~ederevea] OST uses a simple check to determine if to run in RAM or not: {code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000 # ... get_run_path() { local avail_shm avail_shm=$(df --output=avail /dev/shm | sed 1d) [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \ mkdir -p "/dev/shm/ost" && \ echo "/dev/shm/ost/deployment-$SUITE" || \ echo "$PWD/deployment-$SUITE" } {code} This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing) Code quoted above is part of '{{automation/suit.sh}}' in OST: https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=automatio… was (Author: bkorren(a)redhat.com) [~ederevea] OST uses a simple check to determine if to run in RAM or not: {code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000 # ... get_run_path() { local avail_shm avail_shm=$(df --output=avail /dev/shm | sed 1d) [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \ mkdir -p "/dev/shm/ost" && \ echo "/dev/shm/ost/deployment-$SUITE" || \ echo "$PWD/deployment-$SUITE" } {code} This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing) > Increase entropy for hosts > -------------------------- > > Key: OVIRT-1763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > we had a failure in ost that was really hard to debug: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ > There are no failures in the logs and the test itself was terminated by a timeout. > It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. > we need to review this issue and increase the entropy on the hosts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510756591-26566-475 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren edited comment on OVIRT-1763 at 11/15/17 2:36 PM:</h3> <p>[~ederevea] OST uses a simple check to determine if to run in RAM or not:</p> <p>{code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000</p> <p># …</p> <p>get_run_path() {</p> <pre>local avail_shm avail_shm=$(df --output=avail /dev/shm | sed 1d) [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \ mkdir -p "/dev/shm/ost" && \ echo "/dev/shm/ost/deployment-$SUITE" || \ echo "$PWD/deployment-$SUITE"</pre> <p>} {code}</p> <p>This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing)</p> <p>Code quoted above is part of ‘{{automation/suit.sh}}’ in OST: <a href="https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=automatio…">https://gerrit.ovirt.org/gitweb?p=ovirt-system-tests.git;a=blob;f=automatio…</a></p> <p>was (Author: bkorren(a)redhat.com) [~ederevea] OST uses a simple check to determine if to run in RAM or not:</p> <p>{code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000</p> <p># …</p> <p>get_run_path() {</p> <pre>local avail_shm avail_shm=$(df --output=avail /dev/shm | sed 1d) [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \ mkdir -p "/dev/shm/ost" && \ echo "/dev/shm/ost/deployment-$SUITE" || \ echo "$PWD/deployment-$SUITE"</pre> <p>} {code}</p> <p>This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing)</p> <blockquote><h3>Increase entropy for hosts</h3> <pre> Key: OVIRT-1763 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra</pre> <p>we had a failure in ost that was really hard to debug: <a href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/</a> There are no failures in the logs and the test itself was terminated by a timeout. It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. we need to review this issue and increase the entropy on the hosts.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510756591-26566-475--

1 0

[JIRA] (OVIRT-1763) Increase entropy for hosts
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1763: ------------------------------------- [~ederevea] OST uses a simple check to determine if to run in RAM or not: {code} # if above RAM_THRESHOLD KBs are available in /dev/shm, run there RAM_THRESHOLD=15000000 # ... get_run_path() { local avail_shm avail_shm=$(df --output=avail /dev/shm | sed 1d) [[ "$avail_shm" -ge "$RAM_THRESHOLD" ]] && \ mkdir -p "/dev/shm/ost" && \ echo "/dev/shm/ost/deployment-$SUITE" || \ echo "$PWD/deployment-$SUITE" } {code} This seems to be 15G so we need to figure out why wasn't this available when these lines ran (These lines are amount the very first things that run when an OST suit starts up, so its unlikely to be cause by anything the suit is doing) > Increase entropy for hosts > -------------------------- > > Key: OVIRT-1763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > we had a failure in ost that was really hard to debug: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ > There are no failures in the logs and the test itself was terminated by a timeout. > It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. > we need to review this issue and increase the entropy on the hosts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510754998-15183-222 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1767: -------------------------------- Description: One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: https://gerrit.googlesource.com/gitiles/ Another plugin to consider is the one for using GitBlit: https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… Gitblit is another Java based Gir bowser: http://gitblit.com/features.html was: There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: https://gerrit.googlesource.com/gitiles/ > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: gerrit > > One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ > Another plugin to consider is the one for using GitBlit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitblit is another Java based Gir bowser: > http://gitblit.com/features.html -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510754998-15183-222 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1767:</h3> <pre>Description:</pre> <p>One of the faults of our Gerrit system is that the source browser look like it belongs to a different century.</p> <p>There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a></p> <p>Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: <a href="https://gerrit.googlesource.com/gitiles/">https://gerrit.googlesource.com/gitiles/</a></p> <p>Another plugin to consider is the one for using GitBlit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a></p> <p>Gitblit is another Java based Gir bowser: <a href="http://gitblit.com/features.html">http://gitblit.com/features.html</a></p> <pre>was:</pre> <p>There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a></p> <p>Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: <a href="https://gerrit.googlesource.com/gitiles/">https://gerrit.googlesource.com/gitiles/</a></p> <blockquote><h3>Look into replacing gitweb for oVirt Gerrit</h3> <pre> Key: OVIRT-1767 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Gerrit/git Reporter: Barak Korren Assignee: infra Labels: gerrit</pre> <p>One of the faults of our Gerrit system is that the source browser look like it belongs to a different century. There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a> Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: <a href="https://gerrit.googlesource.com/gitiles/">https://gerrit.googlesource.com/gitiles/</a> Another plugin to consider is the one for using GitBlit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a> Gitblit is another Java based Gir bowser: <a href="http://gitblit.com/features.html">http://gitblit.com/features.html</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510754998-15183-222--

1 0

[JIRA] (OVIRT-1767) Look into replacing gitweb for oVirt Gerrit
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1767: -------------------------------- Summary: Look into replacing gitweb for oVirt Gerrit (was: Lok into replacing gitweb with gitiles for oVirt Gerrit) > Look into replacing gitweb for oVirt Gerrit > ------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: gerrit > > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0

[JIRA] (OVIRT-1767) Lok into replacing gitweb with gitiles for oVirt Gerrit
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510754699-27980-389 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1767: -------------------------------- Epic Link: OVIRT-403 > Lok into replacing gitweb with gitiles for oVirt Gerrit > ------------------------------------------------------- > > Key: OVIRT-1767 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: gerrit > > There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… > Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: > https://gerrit.googlesource.com/gitiles/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510754699-27980-389 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1767?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1767:</h3> <pre>Epic Link: OVIRT-403</pre> <blockquote><h3>Lok into replacing gitweb with gitiles for oVirt Gerrit</h3> <pre> Key: OVIRT-1767 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Gerrit/git Reporter: Barak Korren Assignee: infra Labels: gerrit</pre> <p>There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a> Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: <a href="https://gerrit.googlesource.com/gitiles/">https://gerrit.googlesource.com/gitiles/</a></p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510754699-27980-389--

1 0

[JIRA] (OVIRT-1767) Lok into replacing gitweb with gitiles for oVirt Gerrit
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510754683-27754-478 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1767: ----------------------------------- Summary: Lok into replacing gitweb with gitiles for oVirt Gerrit Key: OVIRT-1767 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Gerrit/git Reporter: Barak Korren Assignee: infra There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi… Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: https://gerrit.googlesource.com/gitiles/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510754683-27754-478 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1767:</h3> <pre> Summary: Lok into replacing gitweb with gitiles for oVirt Gerrit Key: OVIRT-1767 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1767 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Gerrit/git Reporter: Barak Korren Assignee: infra</pre> <p>There seems to be a Gerrit plugin which allows using Gitiles rather then gitweb in Gerrit: <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#gi…</a></p> <p>Gitiles itself seems to be a more modern Git UI then gitweb, at the very least is supports showing markdown files, which is a staple of modern source browsers: <a href="https://gerrit.googlesource.com/gitiles/">https://gerrit.googlesource.com/gitiles/</a></p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510754683-27754-478--

1 0

[JIRA] (OVIRT-1766) Try out the x-docs gerit plugin
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510754194-21988-487 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1766?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1766: -------------------------------- Epic Link: OVIRT-403 > Try out the x-docs gerit plugin > ------------------------------- > > Key: OVIRT-1766 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1766 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git > Reporter: Barak Korren > Assignee: infra > Labels: documentation, gerrit > > The x-docs plugin seems to enable Gerrit to expose markdown files from projects formatted to HTML, this can be useful as an auto-generator for project docs. > https://gerrit-review.googlesource.com/Documentation/config-plugins.html#x-… > We might be able to use this as an '{{*.ovirt.org}}' replacement for doc URLs which currently point to GitHub or ReadTheDocs... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510754194-21988-487 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1766?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1766:</h3> <pre>Epic Link: OVIRT-403</pre> <blockquote><h3>Try out the x-docs gerit plugin</h3> <pre> Key: OVIRT-1766 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1766 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Barak Korren Assignee: infra Labels: documentation, gerrit</pre> <p>The x-docs plugin seems to enable Gerrit to expose markdown files from projects formatted to HTML, this can be useful as an auto-generator for project docs. <a href="https://gerrit-review.googlesource.com/Documentation/config-plugins.html#x-…">https://gerrit-review.googlesource.com/Documentation/config-plugins.html#x-…</a> We might be able to use this as an ‘{{*.ovirt.org}}’ replacement for doc URLs which currently point to GitHub or ReadTheDocs…</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510754194-21988-487--

1 0

[JIRA] (OVIRT-1766) Try out the x-docs gerit plugin
by Barak Korren (oVirt JIRA) 15 Nov '17

15 Nov '17

Barak Korren created OVIRT-1766: ----------------------------------- Summary: Try out the x-docs gerit plugin Key: OVIRT-1766 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1766 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Gerrit/git Reporter: Barak Korren Assignee: infra The x-docs plugin seems to enable Gerrit to expose markdown files from projects formatted to HTML, this can be useful as an auto-generator for project docs. https://gerrit-review.googlesource.com/Documentation/config-plugins.html#x-… We might be able to use this as an '{{*.ovirt.org}}' replacement for doc URLs which currently point to GitHub or ReadTheDocs... -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)

1 0

[JIRA] (OVIRT-1763) Increase entropy for hosts
by Evgheni Dereveanchin (oVirt JIRA) 15 Nov '17

15 Nov '17

This is a multi-part message in MIME format... ------------=_1510753169-31571-405 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1763: --------------------------------------------- And I think the difference in speed is caused by this part: 1) successful build 3834 taking 5 minutes to install packages - running in RAM: 02:49:59 [upgrade-from-release-suit] +++ df --output=avail /dev/shm 02:49:59 [upgrade-from-release-suit] +++ sed 1d 02:49:59 [upgrade-from-release-suit] ++ avail_shm=24589620 02:49:59 [upgrade-from-release-suit] ++ [[ 24589620 -ge 15000000 ]] 02:49:59 [upgrade-from-release-suit] ++ mkdir -p /dev/shm/ost 02:49:59 [upgrade-from-release-suit] ++ echo /dev/shm/ost/deployment-upgrade-from-release-suite-master 02:49:59 [upgrade-from-release-suit] + run_path=/dev/shm/ost/deployment-upgrade-from-release-suite-master 2) timed out build 3795 taking 15 minutes to install packages - running on disk: 15:29:24 [upgrade-from-release-suit] ++ local avail_shm 15:29:24 [upgrade-from-release-suit] +++ df --output=avail /dev/shm 15:29:24 [upgrade-from-release-suit] +++ sed 1d 15:29:24 [upgrade-from-release-suit] ++ avail_shm=14540900 15:29:24 [upgrade-from-release-suit] ++ [[ 14540900 -ge 15000000 ]] 15:29:24 [upgrade-from-release-suit] ++ echo /home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master 15:29:24 [upgrade-from-release-suit] + run_path=/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master Logging into the node where build 3795 was running I see 24GB free on the RAM drive when no jobs are running. Not really sure if anything should be on the RAM drive by the time that check is made, based on this we can take action and either clean it up, change the check or increase the timeout. [~bkorren(a)redhat.com] do you know any details about RAM drive specifics for OST? > Increase entropy for hosts > -------------------------- > > Key: OVIRT-1763 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > > we had a failure in ost that was really hard to debug: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/ > There are no failures in the logs and the test itself was terminated by a timeout. > It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. > we need to review this issue and increase the entropy on the hosts. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071) ------------=_1510753169-31571-405 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1763?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin commented on OVIRT-1763:</h3> <p>And I think the difference in speed is caused by this part:</p> <p>1) successful build 3834 taking 5 minutes to install packages – running in RAM: 02:49:59 [upgrade-from-release-suit] +++ df --output=avail /dev/shm 02:49:59 [upgrade-from-release-suit] +++ sed 1d 02:49:59 [upgrade-from-release-suit] ++ avail_shm=24589620 02:49:59 [upgrade-from-release-suit] ++ [[ 24589620 -ge 15000000 ]] 02:49:59 [upgrade-from-release-suit] ++ mkdir -p /dev/shm/ost 02:49:59 [upgrade-from-release-suit] ++ echo /dev/shm/ost/deployment-upgrade-from-release-suite-master 02:49:59 [upgrade-from-release-suit] + run_path=/dev/shm/ost/deployment-upgrade-from-release-suite-master</p> <p>2) timed out build 3795 taking 15 minutes to install packages – running on disk: 15:29:24 [upgrade-from-release-suit] ++ local avail_shm 15:29:24 [upgrade-from-release-suit] +++ df --output=avail /dev/shm 15:29:24 [upgrade-from-release-suit] +++ sed 1d 15:29:24 [upgrade-from-release-suit] ++ avail_shm=14540900 15:29:24 [upgrade-from-release-suit] ++ [[ 14540900 -ge 15000000 ]] 15:29:24 [upgrade-from-release-suit] ++ echo /home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master 15:29:24 [upgrade-from-release-suit] + run_path=/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/deployment-upgrade-from-release-suite-master</p> <p>Logging into the node where build 3795 was running I see 24GB free on the RAM drive when no jobs are running. Not really sure if anything should be on the RAM drive by the time that check is made, based on this we can take action and either clean it up, change the check or increase the timeout. [~bkorren(a)redhat.com] do you know any details about RAM drive specifics for OST?</p> <blockquote><h3>Increase entropy for hosts</h3> <pre> Key: OVIRT-1763 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1763 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra</pre> <p>we had a failure in ost that was really hard to debug: <a href="http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/">http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3795/</a> There are no failures in the logs and the test itself was terminated by a timeout. It took the vms a long time to download packages and install and didi seems to think that this is due to limited entropy on the physical host. we need to review this issue and increase the entropy on the hosts.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100071)</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> ------------=_1510753169-31571-405--

1 0