November 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1740) Mirror sync job for centos-extras-el7 failing
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1740?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1740: -------------------------------- Epic Link: OVIRT-403 > Mirror sync job for centos-extras-el7 failing > --------------------------------------------- > > Key: OVIRT-1740 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1740 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > Priority: High > Labels: mirrors > > The mirror sync job had been failing for a couple of days, here is an example failing run: > http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/8… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1740) Mirror sync job for centos-extras-el7 failing
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

Barak Korren created OVIRT-1740: ----------------------------------- Summary: Mirror sync job for centos-extras-el7 failing Key: OVIRT-1740 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1740 Project: oVirt - virtualization made easy Issue Type: Outage Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Priority: High The mirror sync job had been failing for a couple of days, here is an example failing run: http://jenkins.ovirt.org/job/system-sync_mirrors-centos-extras-el7-x86_64/8… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1735) Upgrade ovirt production in PHX to 4.2 (beta/rc)
by Evgheni Dereveanchin (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509961895-24312-177 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1735?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1735: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Upgrade ovirt production in PHX to 4.2 (beta/rc) > ------------------------------------------------ > > Key: OVIRT-1735 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1735 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > Priority: High > > Since oVirt 4.2 is very stable to our best knowledge, with people even upgraded production environments to alpha build even, we should start working on upgrading ( hosts first and then engine ) our PHX env as well. > Since we have staging env, we can start there with the beta build and then continue to the production one. > This can help us find critical issues that might not be found on normal testing and a chance to fix them before GA. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070) ------------=_1509961895-24312-177 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1735?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1735:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>Upgrade ovirt production in PHX to 4.2 (beta/rc)</h3> <pre> Key: OVIRT-1735 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1735 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri Assignee: Evgheni Dereveanchin Priority: High</pre> <p>Since oVirt 4.2 is very stable to our best knowledge, with people even upgraded production environments to alpha build even, we should start working on upgrading ( hosts first and then engine ) our PHX env as well. Since we have staging env, we can start there with the beta build and then continue to the production one. This can help us find critical issues that might not be found on normal testing and a chance to fix them before GA.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</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> ------------=_1509961895-24312-177--

1 0

[JIRA] (OVIRT-1709) provision Persistent Storage for OpenShift
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1709?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1709: -------------------------------- Component/s: OpenShift > 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: infra > 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#100070)

1 0

[JIRA] (OVIRT-1709) provision Persistent Storage for OpenShift
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1709?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1709: -------------------------------- Labels: openshift (was: ) > 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 > Reporter: Evgheni Dereveanchin > Assignee: infra > 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#100070)

1 0

[JIRA] (OVIRT-1709) provision Persistent Storage for OpenShift
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

This is a multi-part message in MIME format... ------------=_1509957353-14099-169 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1709?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1709: -------------------------------- Priority: High (was: Medium) > 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 > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > 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#100070) ------------=_1509957353-14099-169 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1709?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1709:</h3> <pre>Priority: High (was: Medium)</pre> <blockquote><h3>provision Persistent Storage for OpenShift</h3> <pre> Key: OVIRT-1709 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1709 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: High</pre> <p>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.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)</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> ------------=_1509957353-14099-169--

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Labels: gerrit github reviewers standard-ci (was: ) > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: gerrit, github, reviewers, standard-ci > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[CQ]: 83612,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Nov '17

06 Nov '17

Change 83612,2 (ovirt-engine) 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/83612/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3626/

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1739: ------------------------------------- Current direction is to add support for this in the '{{automation.yaml}}' format so that the default behaviour would be to support the GitHub format. Adding OVIRT-1629 as a blocker to this ticket. > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1739) Unified code owners mechanism between Gerrit and GitHub
by Barak Korren (oVirt JIRA) 06 Nov '17

06 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1739?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1739: -------------------------------- Epic Link: OVIRT-400 > Unified code owners mechanism between Gerrit and GitHub > ------------------------------------------------------- > > Key: OVIRT-1739 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1739 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Gerrit/git, GitHub, oVirt CI > Reporter: Barak Korren > Assignee: infra > > "Code owners" is the mechanism that automatically assigns reviewers to new code patches. > In Gerrit we use the "reviewers" plugin to automatically set reviewers (See OVIRT-1165). > GitHub has its own mechanism: https://github.com/blog/2392-introducing-code-owners > We would like to have a unified way for oVirt devs to do this regardless of the code hosting platform. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0